Get the current page URL and key HTML structure. Useful for debugging when selectors fail.
AI agents call fidelity_page_content to retrieve information from Claude Fidelity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns information (URL and HTML structure) without modifying any state. However, it operates within a financial brokerage context (Fidelity Investments), meaning the page content could expose sensitive account information, credentials, or financial data, warranting a medium severity rating despite being a read-only operation.
From the tool's definition Get the current page URL and key HTML structure. Useful for debugging when selectors fail.
Attacks that exploit this kind of access
Get the current page URL and key HTML structure. Useful for debugging when selectors fail. It is categorised as a Read tool in the Claude Fidelity MCP Server, which means it retrieves data without modifying state.
Register the Claude Fidelity MCP server in PolicyLayer and add a rule for fidelity_page_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 Claude Fidelity. Nothing to install.
fidelity_page_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 fidelity_page_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 fidelity_page_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.
fidelity_page_content is provided by the Claude Fidelity MCP server (tylerflar/claude-fidelity-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 →