Low Risk

get_body_text

获取当前标签页的body的文本内容

How to control get_body_text ↓

AI agents call get_body_text to retrieve information from DrissionPageMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves page content (text from the body element) without creating, modifying, deleting, executing code, or performing financial operations. It is a passive data retrieval operation with no side effects, fitting the Read category. Severity is low because reading text content has minimal security impact even if misused by an agent.

From the tool's definition Tool name 'get_body_text' and description '获取当前标签页的body的文本内容' (retrieves the text content of the body of the current page tab) indicate a read-only operation that extracts text from a webpage without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_body_text gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and DrissionPageMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_body_text:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_body_text": {}
  }
}

get_body_text is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register DrissionPageMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_body_text tool do? +

获取当前标签页的body的文本内容. It is categorised as a Read tool in the DrissionPageMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_body_text? +

Register the DrissionPage MCP server in PolicyLayer and add a rule for get_body_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 DrissionPageMCP. Nothing to install.

What risk level is get_body_text? +

get_body_text is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_body_text? +

Yes. Add a rate_limit block to the get_body_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.

How do I block get_body_text completely? +

Set action: deny in the PolicyLayer policy for get_body_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.

What MCP server provides get_body_text? +

get_body_text is provided by the DrissionPage MCP server (wxhzhwxhzh/drissionpagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DrissionPageMCP tool call.

Deterministic rules across all 37 DrissionPageMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

37 DrissionPageMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.