Get documentation URLs for computing backends. Use this to find where to look up function documentation. Call without args to see all backends, or specify backend to get specific URLs.
AI agents call doc to retrieve information from Scicompute without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only fetches and returns reference documentation pointers. It does not execute code, modify data, delete anything, or commit financial transactions. It is a straightforward query/lookup operation that returns read-only information to help users find documentation resources.
From the tool's definition Tool retrieves documentation URLs for computing backends with 'Get documentation URLs' and 'find where to look up function documentation'.
Attacks that exploit this kind of access
Get documentation URLs for computing backends. Use this to find where to look up function documentation. Call without args to see all backends, or specify backend to get specific URLs. It is categorised as a Read tool in the Scicompute MCP Server, which means it retrieves data without modifying state.
Register the Scicompute MCP server in PolicyLayer and add a rule for doc: 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 Scicompute. Nothing to install.
doc 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 doc 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 doc. 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.
doc is provided by the Scicompute MCP server (sanshanjianke/scicompute-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 →