run_conversion_analysis
AI agents invoke run_conversion_analysis to trigger actions in Ai Analyst. 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.
The 'run_' prefix and 'analysis' suffix indicate this tool executes a defined analytical operation. While not destructive (data is not deleted) or financial, execution of analytical workflows can have side effects such as resource consumption, query performance impact, or generation of new derived metrics that may influence downstream decisions.
From the tool's definition Tool name 'run_conversion_analysis' indicates execution of an analytical workflow. Description is empty, limiting certainty.
Attacks that exploit this kind of access
run_conversion_analysis. It is categorised as a Execute tool in the Ai Analyst MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ai Analyst MCP server in PolicyLayer and add a rule for run_conversion_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 Ai Analyst. Nothing to install.
run_conversion_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 run_conversion_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 run_conversion_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.
run_conversion_analysis is provided by the Ai Analyst MCP server (sbdk-dev/local-ai-analyst). 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 →