Run local static analyzers (tsc and optional semgrep) and return structured findings.
AI agents invoke run_static_analysis to trigger actions in Context Engine 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.
While static analysis itself is typically benign, the tool executes external processes (TypeScript compiler and semgrep) with effects determined by arguments (codebase path, analyzer configuration). An AI agent could misconfigure analyzers, target sensitive files, or abuse the execution capability for other purposes.
From the tool's definition Tool description states it will 'Run local static analyzers (tsc and optional semgrep)' — this invokes external analysis tools whose behavior depends on codebase content and configured rules.
Documented attack patterns abuse exactly the kind of access run_static_analysis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Context Engine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_static_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"run_static_analysis": {
"limits": [
{
"counter": "run_static_analysis_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_static_analysis 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.
Free to start. No card required.
Run local static analyzers (tsc and optional semgrep) and return structured findings. It is categorised as a Execute tool in the Context Engine MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Context Engine MCP Server MCP server in PolicyLayer and add a rule for run_static_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 Context Engine MCP Server. Nothing to install.
run_static_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_static_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_static_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_static_analysis is provided by the Context Engine MCP Server MCP server (kirachon/context-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Context Engine MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Context Engine MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.