<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Sysdig MCP Server</title><link>https://docs.sysdig.com/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/</link><description>Recent content on Sysdig MCP Server</description><language>en</language><lastBuildDate>Wed, 18 Nov 2026 18:51:53 +0100</lastBuildDate><image><url> https://docs.sysdig.com/icons/sysdig-horizontal.png</url><title>Sysdig MCP Server</title><link>https://docs.sysdig.com/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/</link><description>Sysdig logo</description></image><item><title>Sysdig MCP Server - Hosted MCP Server</title><link>https://docs.sysdig.com/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#hosted-mcp-server</link><description>The hosted server is reachable over HTTPS, per region, and authenticated with OAuth. This is the recommended way to connect.</description><content:encoded>&lt;p>The hosted server is reachable over HTTPS, per region, and authenticated with OAuth. This is the recommended way to connect.&lt;/p></content:encoded><guid isPermaLink="false">Hosted MCP Server</guid></item><item><title>Sysdig MCP Server - Set Up Sysdig Monitor MCP Server</title><link>https://docs.sysdig.com/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#set-up-sysdig-monitor-mcp-server</link><description>To start using the Sysdig MCP Server for Sysdig Monitor, register it once with your AI client and authenticate through a one-time OAuth sign-in. The instructions below use Claude Code as an example, but it is possible to register with any MCP-capable client.</description><content:encoded><![CDATA[<p>To start using the Sysdig MCP Server for Sysdig Monitor, register it once with your AI client and authenticate through a one-time OAuth sign-in. The instructions below use Claude Code as an example, but it is possible to register with any MCP-capable client.</p>

<h3 id="prerequisites">Prerequisites</h3>
<ul>

<li>A Sysdig Monitor SaaS account in a <a href="/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#find-your-regions-url">supported region</a></li>

<li>An MCP-capable AI client, such as Claude Code, Cursor, OpenAI Codex, OpenCode, or Claude Desktop</li>

<li>Network connectivity from your client to your region&rsquo;s Sysdig endpoint</li>

<li>A browser for the one-time OAuth sign-in, or a Sysdig Monitor API token. See <a href="/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#authenticate-with-an-api-token">Authenticate with an API Token</a></li>

<li>To use <code>fetch_live_logs</code>: <a href="/en/sysdig-monitor/advisor-troubleshooting/#live-logs">Live Logs</a> available on your clusters</li>
</ul>

<div class='row alert d-flex infobox infobox--note'>
  <div class="ps-0 col-md-auto">
  <i class='fas fa-info-circle fa-lg'></i>
  </div>
  <div class="ps-0 col infobox__contents">

<p>Rate limits are applied per customer: a maximum of 20 requests every 10 seconds and 5 concurrent calls at any time.</p>
  </div>
</div>

<p>The hosted server uses OAuth by default, so you don&rsquo;t need an API token. For a service account, or a client that cannot open a browser, you can <a href="/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#authenticate-with-an-api-token">authenticate with an API token</a> instead.</p>

<h3 id="find-your-regions-url">Find Your Region&rsquo;s URL</h3>
<p>The hosted server lives at <code>&lt;region-url&gt;/mcp/monitor</code>. Identify your region from the <strong>Sysdig UI URL</strong> you see in your browser when signed in to Sysdig Monitor, then use the matching <strong>MCP Server URL</strong> in the registration steps below.</p>
<table>
	<thead>
			<tr>
					<th>Region</th>
					<th>Code</th>
					<th>Sysdig UI URL</th>
					<th>MCP Server URL</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>US East (N. Virginia)</td>
					<td><code>us1</code></td>
					<td><code>https://app.sysdigcloud.com</code></td>
					<td><code>https://app.sysdigcloud.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>US West AWS (Oregon)</td>
					<td><code>us2</code></td>
					<td><code>https://us2.app.sysdig.com</code></td>
					<td><code>https://us2.app.sysdig.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>US West GCP (Oregon)</td>
					<td><code>us4</code></td>
					<td><code>https://app.us4.sysdig.com</code></td>
					<td><code>https://app.us4.sysdig.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>EU Central (Frankfurt)</td>
					<td><code>eu1</code></td>
					<td><code>https://eu1.app.sysdig.com</code></td>
					<td><code>https://eu1.app.sysdig.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>EU North (Stockholm)</td>
					<td><code>eu2</code></td>
					<td><code>https://app.eu2.sysdig.com</code></td>
					<td><code>https://app.eu2.sysdig.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>Asia Pacific (Sydney)</td>
					<td><code>au1</code></td>
					<td><code>https://app.au1.sysdig.com</code></td>
					<td><code>https://app.au1.sysdig.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>Asia Pacific (Mumbai)</td>
					<td><code>in1</code></td>
					<td><code>https://app.in1.sysdig.com</code></td>
					<td><code>https://app.in1.sysdig.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>Middle East (Dammam)</td>
					<td><code>me2</code></td>
					<td><code>https://app.me2.sysdig.com</code></td>
					<td><code>https://app.me2.sysdig.com/mcp/monitor</code></td>
			</tr>
			<tr>
					<td>Asia Pacific (Tokyo)</td>
					<td><code>jp1</code></td>
					<td><code>https://app.jp1.sysdig.com</code></td>
					<td><code>https://app.jp1.sysdig.com/mcp/monitor</code></td>
			</tr>
	</tbody>
</table>

<h3 id="register-the-server-in-claude-code">Register the Server in Claude Code</h3>
<p>Run the following command in your terminal, substituting your region&rsquo;s MCP Server URL from the table above:</p>
<div class="highlight">
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">claude mcp add --transport http monitor-mcp-server https://us2.app.sysdig.com/mcp/monitor
</span></span></code></pre></div>
<p>Keep the server name as <code>monitor-mcp-server</code>. The registration is saved automatically; there is no environment variable to set or persist. Add <code>--scope user</code> to make the registration available across all your projects, or use the default (<code>local</code>) for the current project only. Restart any Claude Code session that was open before you ran the command.</p>

<h3 id="authenticate">Authenticate</h3>
<p>The first time your AI client calls a Sysdig tool, run <code>/mcp</code>, select <code>monitor-mcp-server</code>, and select <strong>Authenticate</strong>. Your browser opens for a one-time OAuth sign-in, and the session is then authenticated for the rest of your work.</p>

<h3 id="configure-other-ai-clients">Configure Other AI Clients</h3>
<p>Every MCP-capable client can use the same hosted server: an HTTP MCP server at your region&rsquo;s <code>/mcp/monitor</code> URL, authenticated through OAuth. The exact steps differ per client (a config file, a settings panel, or a CLI command), but the essentials are identical:</p>

<ul>

<li><strong>Transport:</strong> HTTP (streamable)</li>

<li><strong>Server name:</strong> <code>monitor-mcp-server</code></li>

<li><strong>URL:</strong> your region&rsquo;s MCP Server URL, for example <code>https://us2.app.sysdig.com/mcp/monitor</code></li>

<li><strong>Authentication:</strong> OAuth by default. The client drives the browser flow on first request. To use an API token instead, see <a href="/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#authenticate-with-an-api-token">Authenticate with an API Token</a>.</li>
</ul>


<p>For clients that follow the standard MCP server schema, use a configuration snippet like the following. Edit the URL to match your region:</p>
<div class="highlight">
<pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl">  <span class="nt">&#34;mcpServers&#34;</span><span class="p">:</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">    <span class="nt">&#34;monitor-mcp-server&#34;</span><span class="p">:</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">      <span class="nt">&#34;type&#34;</span><span class="p">:</span> <span class="s2">&#34;http&#34;</span><span class="p">,</span>
</span></span><span class="line"><span class="cl">      <span class="nt">&#34;url&#34;</span><span class="p">:</span> <span class="s2">&#34;https://us2.app.sysdig.com/mcp/monitor&#34;</span>
</span></span><span class="line"><span class="cl">    <span class="p">}</span>
</span></span><span class="line"><span class="cl">  <span class="p">}</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span>
</span></span></code></pre></div>
<p>Consult your client&rsquo;s MCP documentation for the exact configuration-file location and reload procedure.</p>
<div class='row alert d-flex infobox infobox--note'>
  <div class="ps-0 col-md-auto">
  <i class='fas fa-info-circle fa-lg'></i>
  </div>
  <div class="ps-0 col infobox__contents">

<p><strong>Multi-region:</strong> There is no region-independent URL. Set the URL for your tenant’s region, and update it if you move to a different region.</p>
  </div>
</div>

<h3 id="authenticate-with-an-api-token">Authenticate with an API Token</h3>
<p>Use an API token for a service account, or for an AI client that cannot open a browser for the OAuth sign-in. The server accepts a Sysdig Monitor API token in a standard <code>Authorization: Bearer</code> header, and then acts with the permissions of the user or service account that owns the token. To get a token, see <a href="/en/administration/retrieve-the-sysdig-api-token">Retrieve the Sysdig API Token</a>.</p>

<p>In Claude Code, add the header when you register the server:</p>
<div class="highlight">
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">claude mcp add --transport http monitor-mcp-server https://us2.app.sysdig.com/mcp/monitor --header <span class="s2">&#34;Authorization: Bearer &lt;your-api-token&gt;&#34;</span>
</span></span></code></pre></div>
<p>For other clients, add a <code>headers</code> entry to the server configuration:</p>
<div class="highlight">
<pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl">  <span class="nt">&#34;mcpServers&#34;</span><span class="p">:</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">    <span class="nt">&#34;monitor-mcp-server&#34;</span><span class="p">:</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">      <span class="nt">&#34;type&#34;</span><span class="p">:</span> <span class="s2">&#34;http&#34;</span><span class="p">,</span>
</span></span><span class="line"><span class="cl">      <span class="nt">&#34;url&#34;</span><span class="p">:</span> <span class="s2">&#34;https://us2.app.sysdig.com/mcp/monitor&#34;</span><span class="p">,</span>
</span></span><span class="line"><span class="cl">      <span class="nt">&#34;headers&#34;</span><span class="p">:</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">        <span class="nt">&#34;Authorization&#34;</span><span class="p">:</span> <span class="s2">&#34;Bearer &lt;your-api-token&gt;&#34;</span>
</span></span><span class="line"><span class="cl">      <span class="p">}</span>
</span></span><span class="line"><span class="cl">    <span class="p">}</span>
</span></span><span class="line"><span class="cl">  <span class="p">}</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span>
</span></span></code></pre></div>
<p>With a token, the client skips the OAuth sign-in. Treat the token as a secret, and keep it out of configuration files that you share or commit, such as a project <code>.mcp.json</code>.</p>

<h3 id="verify-the-connection">Verify the Connection</h3>
<p>In Claude Code, run:</p>
<div class="highlight">
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">claude mcp list
</span></span></code></pre></div>
<p>You should see a <code>monitor-mcp-server</code> row with the status <code>connected</code>. In a running session, <code>/mcp</code> opens the MCP status panel, which shows the authentication state for each server.</p>

<p>For an end-to-end check, ask the agent to call <code>get_current_user</code>. If it returns your Sysdig user profile, the server is reachable and authenticated.</p>

<h3 id="troubleshooting">Troubleshooting</h3><table>
	<thead>
			<tr>
					<th>Symptom</th>
					<th>Cause and fix</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>monitor-mcp-server</code> is missing from <code>claude mcp list</code></td>
					<td>The server was never registered. Run the <a href="/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#register-the-server-in-claude-code">registration command</a> with your region&rsquo;s MCP Server URL.</td>
			</tr>
			<tr>
					<td>Listed, but not <code>connected</code></td>
					<td>The server needs authentication. In a session, run <code>/mcp</code>, select <code>monitor-mcp-server</code>, and select <strong>Authenticate</strong>. If OAuth previously succeeded but tools stopped working, the session token may have expired; authenticate again.</td>
			</tr>
			<tr>
					<td>Network or DNS errors, or the wrong tenant responds</td>
					<td>The registered URL is for the wrong region. Run <code>claude mcp remove monitor-mcp-server</code>, then re-add it with the correct MCP Server URL from the <a href="/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#find-your-regions-url">region table</a>.</td>
			</tr>
			<tr>
					<td>The wrong server responds regardless of your registration</td>
					<td>A <code>monitor-mcp-server</code> entry hardcoded in a project <code>.mcp.json</code>, <code>.claude/settings.local.json</code>, or <code>~/.claude/settings.json</code> takes precedence. Remove or correct that entry.</td>
			</tr>
			<tr>
					<td><code>fetch_live_logs</code> returns no logs or fails</td>
					<td>Live Logs is not available for the cluster or for your role. See <a href="/en/sysdig-monitor/advisor-troubleshooting/#live-logs">Live Logs</a>.</td>
			</tr>
	</tbody>
</table>]]></content:encoded><guid isPermaLink="false">Set Up Sysdig Monitor MCP Server</guid></item><item><title>Sysdig MCP Server - API Permissions</title><link>https://docs.sysdig.com/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#api-permissions</link><description>The MCP server acts with the permissions of the account that authenticates: your own Sysdig user when you sign in with OAuth, or the user or service account that owns the API token. You can use the tools that account already has access to.</description><content:encoded><![CDATA[<p>The MCP server acts with the permissions of the account that authenticates: your own Sysdig user when you sign in with OAuth, or the user or service account that owns the API token. You can use the tools that account already has access to.</p>

<h3 id="assign-permissions">Assign Permissions</h3>
<p>To assign permissions to a user, do the following:</p>

<ol>

<li>Go to <strong>Settings</strong> &gt; <strong>Roles</strong>.</li>

<li>Create a role with the required permissions. See <a href="/en/administration/roles-administration/">Roles</a>.</li>

<li>Assign the role to a service account or user.</li>

<li>Sign in to the MCP server as that user, or use the service account&rsquo;s API token. See <a href="/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#authenticate-with-an-api-token">Authenticate with an API Token</a>.</li>
</ol>]]></content:encoded><guid isPermaLink="false">API Permissions</guid></item><item><title>Sysdig MCP Server - Security Considerations</title><link>https://docs.sysdig.com/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#security-considerations</link><description>Area Description Authentication Use OAuth where you can. If you use an API token, store it as a secret, give the service account only the permissions it needs, and rotate the token regularly. Input Validation &amp;amp; Prompt Sanitization Guard against prompt injection. Validate and sanitize client inputs before execution. Least Privilege &amp;amp; Scope Limiting Grant only the minimal required permissions for each use case. Users who only troubleshoot do not need permissions to manage users, teams, or roles. Account Changes User, team, and role tools change other users&amp;rsquo; access, and deletions cannot be undone. Require approval before your AI client runs them. Sensitive Output Live logs and pod manifests can contain secrets. Redaction is best-effort, so treat the output as sensitive. Context &amp;amp; Tenant Isolation Ensure clients and tenants are isolated to prevent data leakage across contexts. Audit Logging &amp;amp; Monitoring Log client requests, tool invocations, and API interactions. Monitor for anomalies or abuse. Transport Security The hosted server is reachable over HTTPS and authenticated with OAuth. If you run the community server for experimentation, use TLS for HTTP transports and never send API tokens in query parameters.</description><content:encoded><![CDATA[<table>
	<thead>
			<tr>
					<th>Area</th>
					<th>Description</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><strong>Authentication</strong></td>
					<td>Use OAuth where you can. If you use an API token, store it as a secret, give the service account only the permissions it needs, and rotate the token regularly.</td>
			</tr>
			<tr>
					<td><strong>Input Validation &amp; Prompt Sanitization</strong></td>
					<td>Guard against prompt injection. Validate and sanitize client inputs before execution.</td>
			</tr>
			<tr>
					<td><strong>Least Privilege &amp; Scope Limiting</strong></td>
					<td>Grant only the minimal required permissions for each use case. Users who only troubleshoot do not need permissions to manage users, teams, or roles.</td>
			</tr>
			<tr>
					<td><strong>Account Changes</strong></td>
					<td>User, team, and role tools change other users&rsquo; access, and deletions cannot be undone. Require approval before your AI client runs them.</td>
			</tr>
			<tr>
					<td><strong>Sensitive Output</strong></td>
					<td>Live logs and pod manifests can contain secrets. Redaction is best-effort, so treat the output as sensitive.</td>
			</tr>
			<tr>
					<td><strong>Context &amp; Tenant Isolation</strong></td>
					<td>Ensure clients and tenants are isolated to prevent data leakage across contexts.</td>
			</tr>
			<tr>
					<td><strong>Audit Logging &amp; Monitoring</strong></td>
					<td>Log client requests, tool invocations, and API interactions. Monitor for anomalies or abuse.</td>
			</tr>
			<tr>
					<td><strong>Transport Security</strong></td>
					<td>The hosted server is reachable over HTTPS and authenticated with OAuth. If you run the community server for experimentation, use TLS for HTTP transports and never send API tokens in query parameters.</td>
			</tr>
	</tbody>
</table>]]></content:encoded><guid isPermaLink="false">Security Considerations</guid></item><item><title>Sysdig MCP Server - Available Tools</title><link>https://docs.sysdig.com/en/sysdig-monitor/monitor-ai/sysdig-monitor-mcp-server/#available-tools</link><description>The MCP server exposes tools that your AI client can call on your behalf.</description><content:encoded><![CDATA[<p>The MCP server exposes tools that your AI client can call on your behalf.</p>
<div class='row alert d-flex infobox infobox--warning'>
  <div class="ps-0 col-md-auto">
  <i class='fas fa-exclamation-circle fa-lg'></i>
  </div>
  <div class="ps-0 col infobox__contents">

<p>The tools in <a href="/en/#users-teams-and-roles">Users, Teams, and Roles</a> change other users’ access with your permissions: they can delete or disable users, change roles and team memberships, and send invitation emails. Deletions cannot be undone, so require approval before your AI client runs these tools.</p>
  </div>
</div>

<p>This list is not exhaustive and changes between releases. For the current list, connect to the server and view its tools in your AI client. In Claude Code, run <code>/mcp</code> and select <code>monitor-mcp-server</code>.</p>

<p>Available tools include:</p>

<h3 id="kubernetes-inventory">Kubernetes Inventory</h3><table>
	<thead>
			<tr>
					<th>Tool</th>
					<th>Description</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>k8s_list_clusters</code></td>
					<td>List the Kubernetes clusters reporting to Sysdig Monitor.</td>
			</tr>
			<tr>
					<td><code>k8s_list_namespaces</code></td>
					<td>List namespaces, optionally with their Kubernetes labels, such as team or environment.</td>
			</tr>
			<tr>
					<td><code>k8s_list_nodes</code></td>
					<td>List nodes, with their IP address, kubelet, container runtime, and OS versions.</td>
			</tr>
			<tr>
					<td><code>k8s_list_workloads</code></td>
					<td>List workloads and their replica counts by status: desired, ready, running, or unavailable.</td>
			</tr>
			<tr>
					<td><code>k8s_list_pod_containers</code></td>
					<td>List the containers in pods, with their workload, node, and image.</td>
			</tr>
			<tr>
					<td><code>k8s_count_pods_by_scope</code></td>
					<td>Count pods per namespace.</td>
			</tr>
	</tbody>
</table>

<h3 id="kubernetes-troubleshooting">Kubernetes Troubleshooting</h3><table>
	<thead>
			<tr>
					<th>Tool</th>
					<th>Description</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>get_workload_metric</code></td>
					<td>Retrieve a troubleshooting metric for workloads, such as CPU or memory usage, restarts, HTTP errors, or latency.</td>
			</tr>
			<tr>
					<td><code>get_node_metric</code></td>
					<td>Retrieve a troubleshooting metric for nodes, such as high usage, memory or PID pressure, or overcommit.</td>
			</tr>
			<tr>
					<td><code>fetch_live_logs</code></td>
					<td>Fetch a short window of real-time logs from a workload&rsquo;s running pods, including the previous container after a restart. Secrets are redacted on a best-effort basis.</td>
			</tr>
			<tr>
					<td><code>get_pod_yaml</code></td>
					<td>Fetch the YAML manifest of a pod. The manifest can contain plaintext secrets, such as environment variables. Treat the output as sensitive.</td>
			</tr>
			<tr>
					<td><code>get_image_version</code></td>
					<td>Show which container images a workload ran over a 24-hour window, including rollouts.</td>
			</tr>
			<tr>
					<td><code>get_namespace_resource_quotas</code></td>
					<td>Show the ResourceQuota limits, usage, and remaining headroom in a namespace.</td>
			</tr>
			<tr>
					<td><code>get_pvc_status</code></td>
					<td>Show the status of PersistentVolumeClaims, such as phase, storage class, and requested size.</td>
			</tr>
			<tr>
					<td><code>get_storage_classes</code></td>
					<td>List the StorageClasses available in a cluster.</td>
			</tr>
	</tbody>
</table>

<h3 id="metrics-and-promql">Metrics and PromQL</h3><table>
	<thead>
			<tr>
					<th>Tool</th>
					<th>Description</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>promql_query</code></td>
					<td>Run a PromQL instant query.</td>
			</tr>
			<tr>
					<td><code>promql_query_range</code></td>
					<td>Run a PromQL range query and return the raw series.</td>
			</tr>
			<tr>
					<td><code>get_metric_chart</code></td>
					<td>Render an interactive time-series chart of a metric.</td>
			</tr>
			<tr>
					<td><code>search_metrics</code> / <code>search_labels</code> / <code>search_label_values</code></td>
					<td>Discover metrics, their labels, and label values to build PromQL queries.</td>
			</tr>
	</tbody>
</table>

<h3 id="identity-and-account-settings">Identity and Account Settings</h3><table>
	<thead>
			<tr>
					<th>Tool</th>
					<th>Description</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>get_current_user</code></td>
					<td>Retrieve the profile of the authenticated user.</td>
			</tr>
			<tr>
					<td><code>get_user_permissions</code></td>
					<td>Retrieve the permissions of the authenticated user in their active team.</td>
			</tr>
			<tr>
					<td><code>get_customer_settings</code></td>
					<td>Retrieve your tenant&rsquo;s Sysdig settings, including which features are enabled.</td>
			</tr>
	</tbody>
</table>

<h3 id="users-teams-and-roles">Users, Teams, and Roles</h3><table>
	<thead>
			<tr>
					<th>Tool</th>
					<th>Description</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>list_users</code> / <code>get_user</code></td>
					<td>List users, or retrieve one user by ID.</td>
			</tr>
			<tr>
					<td><code>list_teams</code> / <code>get_team</code></td>
					<td>List teams, or retrieve one team by ID.</td>
			</tr>
			<tr>
					<td><code>list_roles</code> / <code>get_default_role</code></td>
					<td>List roles, or retrieve a built-in default role by name.</td>
			</tr>
			<tr>
					<td><code>create_user</code></td>
					<td>Create a user. Optionally sends an invitation email to the user.</td>
			</tr>
			<tr>
					<td><code>update_user</code></td>
					<td>Update a user, or enable or disable them without deleting them.</td>
			</tr>
			<tr>
					<td><code>delete_user</code></td>
					<td>Delete a user and their team memberships. This action cannot be undone.</td>
			</tr>
			<tr>
					<td><code>create_team</code></td>
					<td>Create a team.</td>
			</tr>
			<tr>
					<td><code>update_team</code></td>
					<td>Update a team.</td>
			</tr>
			<tr>
					<td><code>delete_team</code></td>
					<td>Delete a team and all its memberships. This action cannot be undone.</td>
			</tr>
			<tr>
					<td><code>save_team_membership</code></td>
					<td>Add a user to a team, or change their role on it.</td>
			</tr>
	</tbody>
</table>]]></content:encoded><guid isPermaLink="false">Available Tools</guid></item></channel></rss>