AI agents use pptx_add_responsive_card_row to create or update resources in Pptx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pptx environment.
Based on naming convention and sibling tools, this tool creates or adds content to a PowerPoint presentation, which is reversible modification of data (Write category). Severity is medium because misuse could create unwanted slides/content requiring manual cleanup, but changes are editable and not destructive.
From the tool's definition Tool name includes 'add' prefix, consistent with sibling tools 'pptx_add_bullet_block', 'pptx_add_chart', 'pptx_add_image', etc., all of which create or modify presentation content. Description is empty, limiting precision.
Attacks that exploit this kind of access
pptx_add_responsive_card_row. It is categorised as a Write tool in the Pptx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pptx MCP server in PolicyLayer and add a rule for pptx_add_responsive_card_row: 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 Pptx. Nothing to install.
pptx_add_responsive_card_row 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 pptx_add_responsive_card_row 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 pptx_add_responsive_card_row. 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.
pptx_add_responsive_card_row is provided by the Pptx MCP server (knorq-ai/pptx-mcp-server). 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 →