AI agents invoke evaluate_code to trigger actions in Powerpoint. 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 name 'evaluate_code' indicates this tool runs or evaluates code, which falls under Execute. Without a description, the exact scope is unknown, but code evaluation typically carries high risk as an AI agent could misuse it to run arbitrary code. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'evaluate_code' strongly implies execution of arbitrary code; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access evaluate_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Powerpoint, and nothing reaches the server without passing your rules. This is the rule we recommend for evaluate_code:
{
"version": "1",
"default": "deny",
"tools": {
"evaluate_code": {
"limits": [
{
"counter": "evaluate_code_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}evaluate_code 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.
evaluate_code. It is categorised as a Execute tool in the Powerpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Powerpoint MCP server in PolicyLayer and add a rule for evaluate_code: 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 Powerpoint. Nothing to install.
evaluate_code 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 evaluate_code 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 evaluate_code. 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.
evaluate_code is provided by the Powerpoint MCP server (juanocampo400/powerpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Powerpoint, 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.
17 Powerpoint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.