Fetch webpage content and convert to specified format. Supports Markdown, HTML, and plain text.
AI agents call get_webpage_content to retrieve information from Spider MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and converts existing webpage content to different formats. It has no side effects—it does not create, modify, delete, or execute arbitrary code. The conversion to different formats is a read-only transformation of data already retrieved. This is a classic Read category operation with low blast radius if misused by an agent.
From the tool's definition Tool name 'get_webpage_content' and description 'Fetch webpage content' indicate retrieval without modification. Supported output formats (Markdown, HTML, plain text) are presentation formats only, confirming no data is altered or deleted.
Attacks that exploit this kind of access
Fetch webpage content and convert to specified format. Supports Markdown, HTML, and plain text. It is categorised as a Read tool in the Spider MCP MCP Server, which means it retrieves data without modifying state.
Register the Spider MCP server in PolicyLayer and add a rule for get_webpage_content: 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 Spider MCP. Nothing to install.
get_webpage_content 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 get_webpage_content 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 get_webpage_content. 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.
get_webpage_content is provided by the Spider MCP server (yc9yc/spider-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →