AI agents use modify_table_cell to create or update resources in Powerpoint — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Powerpoint environment.
This tool modifies table content within a PowerPoint presentation. It is Write-category because it changes data reversibly (cell contents can be edited or undone). It is not Execute because it does not run arbitrary code—it is constrained to table cell modification. Severity is medium because misuse could corrupt presentation content, but the blast radius is limited to a single cell's data and is reversible.
From the tool's definition Tool name is 'modify_table_cell' on a PowerPoint editing server. Sibling tools include 'add_table', 'delete_shape', and 'find_and_replace', confirming this server modifies presentations.
Documented attack patterns abuse exactly the kind of access modify_table_cell 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 modify_table_cell:
{
"version": "1",
"default": "deny",
"tools": {
"modify_table_cell": {
"limits": [
{
"counter": "modify_table_cell_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_table_cell stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
modify_table_cell. It is categorised as a Write tool in the Powerpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Powerpoint MCP server in PolicyLayer and add a rule for modify_table_cell: 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.
modify_table_cell is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the modify_table_cell 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 modify_table_cell. 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.
modify_table_cell 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.