AI agents call get_doc_page to retrieve information from DocShark without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple retrieval of existing documentation data without creating, modifying, deleting, or executing any operations. It has no side effects and returns static content. The blast radius of misuse is minimal—an agent could retrieve documentation it shouldn't have access to, but cannot alter or delete it, making this a low-severity read operation.
From the tool's definition Tool retrieves documentation pages as markdown with no modification capability described. The name 'get_doc_page' and description 'Retrieve complete documentation page' indicate a read-only query operation.
Attacks that exploit this kind of access
Retrieve complete documentation page as markdown. It is categorised as a Read tool in the DocShark MCP Server, which means it retrieves data without modifying state.
Register the DocShark MCP server in PolicyLayer and add a rule for get_doc_page: 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 DocShark. Nothing to install.
get_doc_page 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_doc_page 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_doc_page. 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_doc_page is provided by the DocShark MCP server (michael-obele/docshark). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_doc_page is one line of DocShark's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →