content_get_text
Get the plain text content of the current page (no HTML tags).
This record as markdown: /tools/mcp-anything/content-get-text.md
What content_get_text does on Mcp Anything
AI agents call content_get_text 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 content_get_text is rated Low
This tool retrieves and queries existing data (page content) without creating, modifying, executing code, deleting, or moving money. It is a passive read operation that has no side effects on the system or data state.
From the tool's definition Tool name 'content_get_text' and description 'Get the plain text content of the current page (no HTML tags)' clearly indicate a retrieval operation with no modification capabilities.
Attacks that exploit this kind of access
The rule that runs content_get_text 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 content_get_text, this is the rule to start with:
content_get_text 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 content_get_text call is checked against it from then on.
Questions about content_get_text
Get the plain text content of the current page (no HTML tags). 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 content_get_text: 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.
content_get_text 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 content_get_text 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 content_get_text. 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.
content_get_text 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