on_page_content_parsing

This endpoint allows parsing the content on any page you specify and will return the structured content of the target page, including link URLs, anchors, headings, and textual content.

Server Dataforseo dataforseo-mcp-server
Category Read
Risk class Low
Parameters 41 required

What on_page_content_parsing does on Dataforseo

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

ParameterTypeRequiredDescription
url string Yes URL of the page to parse
accept_language string Accept-Language header value
custom_user_agent string Custom User-Agent header
enable_javascript boolean Enable JavaScript rendering

Parameters from the server's own tool schema.

Why on_page_content_parsing needs a policy

This is a data retrieval operation that fetches and structures existing content from a webpage. The tool parses and returns information without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal — an agent could fetch unwanted public web content, but this causes no damage or unauthorized state changes.

From the tool's definition The tool 'allows parsing the content on any page you specify and will return the structured content' — it retrieves and returns data (link URLs, anchors, headings, textual content) with no modification or side effects.

Risk signalsAccepts URL/endpoint input (url)

Questions about on_page_content_parsing

What does the on_page_content_parsing tool do? +

This endpoint allows parsing the content on any page you specify and will return the structured content of the target page, including link URLs, anchors, headings, and textual content. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.

What parameters does on_page_content_parsing accept? +

on_page_content_parsing accepts 4 parameters: url, accept_language, custom_user_agent, enable_javascript. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on on_page_content_parsing? +

Register the Dataforseo MCP server in PolicyLayer and add a rule for on_page_content_parsing: 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 Dataforseo. Nothing to install.

What risk level is on_page_content_parsing? +

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

Can I rate-limit on_page_content_parsing? +

Yes. Add a rate_limit block to the on_page_content_parsing 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 on_page_content_parsing completely? +

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

on_page_content_parsing is provided by the Dataforseo MCP server (dataforseo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.