Analyze a document with a selected prompt and stream the results
AI agents invoke execute_analysis to trigger actions in Legal 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.
This tool executes a third-party LLM analysis pipeline with potentially unpredictable outputs. While not destructive to underlying data, the execution of arbitrary analysis with user-provided prompts on legal documents constitutes a code/operation execution capability.
From the tool's definition Tool name 'execute_analysis' combined with description 'Analyze a document with a selected prompt and stream the results' indicates execution of an analysis operation.
Attacks that exploit this kind of access
Analyze a document with a selected prompt and stream the results. It is categorised as a Execute tool in the Legal MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Legal MCP Server MCP server in PolicyLayer and add a rule for execute_analysis: 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 Legal MCP Server. Nothing to install.
execute_analysis is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_analysis 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.
Set action: deny in the PolicyLayer policy for execute_analysis. 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.
execute_analysis is provided by the Legal MCP Server MCP server (mcp-agent766/legal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →