AI agents use ppt_set_table_cell to create or update resources in Ppt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ppt environment.
This tool modifies table cell content and formatting within a PowerPoint presentation. Such modifications are reversible (can be undone/overwritten), making it a Write operation rather than Destructive or Execute. The severity is medium because misuse could corrupt or deface presentation content, but changes can be reverted.
From the tool's definition Tool name 'ppt_set_table_cell' and description 'Set text and/or formatting for a table cell' indicate modification of existing presentation content.
Documented attack patterns abuse exactly the kind of access ppt_set_table_cell gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ppt, and nothing reaches the server without passing your rules. This is the rule we recommend for ppt_set_table_cell:
{
"version": "1",
"default": "deny",
"tools": {
"ppt_set_table_cell": {
"limits": [
{
"counter": "ppt_set_table_cell_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ppt_set_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.
Set text and/or formatting for a table cell. It is categorised as a Write tool in the Ppt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ppt MCP server in PolicyLayer and add a rule for ppt_set_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 Ppt. Nothing to install.
ppt_set_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 ppt_set_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 ppt_set_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.
ppt_set_table_cell is provided by the Ppt MCP server (ykuwai/ppt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 156 Ppt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
156 Ppt tools catalogued and risk-classified — across an index of 42,500+ MCP servers.