Low Risk

fetch_document_links

fetch_document_links

How to control fetch_document_links ↓

What fetch_document_links does on Docy

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

Low Risk

Why fetch_document_links needs a policy

The tool appears to fetch or retrieve document links, which is a read operation with no side effects. No data is modified, deleted, or executed. The empty description lowers confidence slightly, but the function name and context of a documentation server strongly suggest this is a retrieval operation similar to other 'fetch' tools on the server.

From the tool's definition Tool name 'fetch_document_links' indicates retrieval of link data from documents. The description is empty, but the naming pattern aligns with sibling tool 'fetch_documentation_page' which retrieves documentation content without modification.

Documented attack patterns abuse exactly the kind of access fetch_document_links gives an agent:

How to control fetch_document_links

PolicyLayer is an MCP gateway — it sits between your AI agents and Docy, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_document_links:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_document_links": {}
  }
}

fetch_document_links is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Docy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_document_links

What does the fetch_document_links tool do? +

fetch_document_links. It is categorised as a Read tool in the Docy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_document_links? +

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

What risk level is fetch_document_links? +

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

Can I rate-limit fetch_document_links? +

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

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

fetch_document_links is provided by the Docy MCP server (oborchers/mcp-server-docy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docy tool call.

Start from Docy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

3 Docy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.