AI agents call find_element to retrieve information from PowerPoint MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries information about existing slide elements without creating, modifying, deleting, or executing operations. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The low severity reflects minimal blast radius if misused by an AI agent—worst case is information disclosure about presentation structure.
From the tool's definition Tool name 'find_element' and description 'Find elements on a slide based on criteria' indicate a search/query operation with no modification of presentation data.
Documented attack patterns abuse exactly the kind of access find_element gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PowerPoint MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_element:
{
"version": "1",
"default": "deny",
"tools": {
"find_element": {}
}
}find_element is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find elements on a slide based on criteria. It is categorised as a Read tool in the PowerPoint MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PowerPoint MCP Server MCP server in PolicyLayer and add a rule for find_element: 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 MCP Server. Nothing to install.
find_element 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 find_element 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 find_element. 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.
find_element is provided by the PowerPoint MCP Server MCP server (jenstangen1/pptx-xlsx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PowerPoint MCP Server, 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.
37 PowerPoint MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.