analyze_documents · Sigma MCP Server MCP: Risk & Policy

WHAT IT DOES

What analyze_documents does on Sigma MCP Server

AI agents invoke analyze_documents to trigger actions in Sigma MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why analyze_documents needs a policy

The tool runs SQL queries against Sigma documents and analytics data, which constitutes executing code/queries whose effects depend on the SQL arguments provided. While described as filtering/reading, executing arbitrary SQL queries carries elevated risk as the queries could be complex or resource-intensive, and the tool actively runs computation rather than simply retrieving static data.

From the tool's definition 'Analyze Sigma documents using SQL queries to filter data before analysis' and 'Use this after generate_sql_query to get filtered results' — executes SQL queries against documents/analytics data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

analyze_documents Rate-limited

analyze_documents stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_documents": {
      "limits": [
        {
          "counter": "analyze_documents_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sigma MCP Server, so you can run agents against it safely.

FAQ

Questions about analyze_documents

What does the analyze_documents tool do? +

Analyze Sigma documents using SQL queries to filter data before analysis. Use this after generate_sql_query to get filtered results. It is categorised as a Execute tool in the Sigma MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on analyze_documents? +

Register the Sigma MCP Server MCP server in PolicyLayer and add a rule for analyze_documents: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Sigma MCP Server. Nothing to install.

What risk level is analyze_documents? +

analyze_documents is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit analyze_documents? +

Yes. Add a rate_limit block to the analyze_documents rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block analyze_documents completely? +

Set action: deny in the PolicyLayer policy for analyze_documents. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides analyze_documents? +

analyze_documents is provided by the Sigma MCP Server MCP server (ja2z/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.