AI agents call pptx_check_layout to retrieve information from Pptx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name pattern and the context of a PowerPoint editing server indicate this is likely a read-only operation that verifies or retrieves layout information from a presentation. No modification or execution keywords are present. Without description details, confidence is moderate but the category is most consistent with Read operations (retrieve/query).
From the tool's definition Tool name 'pptx_check_layout' suggests a checking/inspection operation. The verb 'check' implies querying or retrieving state without modification. Description is empty, reducing confidence.
Attacks that exploit this kind of access
pptx_check_layout. It is categorised as a Read tool in the Pptx MCP Server, which means it retrieves data without modifying state.
Register the Pptx MCP server in PolicyLayer and add a rule for pptx_check_layout: 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_check_layout is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pptx_check_layout 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_check_layout. 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_check_layout 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 →