This record as markdown: /tools/mcp-anything/doc-get-element.md
What doc_get_element does on Mcp Anything
AI agents call doc_get_element to retrieve information from Mcp Anything without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why doc_get_element is rated Low
This tool retrieves or queries a specific document element by index position. The verb 'Get' and the read-only nature of accessing an element by index with no modification capability place this firmly in the Read category. There is minimal risk—it returns data without altering state. Low severity because misuse would only expose or retrieve existing information, not modify, delete, or execute operations.
From the tool's definition Tool name 'doc_get_element' and description 'Get a specific element by index' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs doc_get_element safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For doc_get_element, this is the rule to start with:
doc_get_element is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every doc_get_element call is checked against it from then on.
Questions about doc_get_element
Get a specific element by index. It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for doc_get_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 Mcp Anything. Nothing to install.
doc_get_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 doc_get_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 doc_get_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.
doc_get_element is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue