Low Risk

get_doc

Get the full content of a specific file. Supports files from .project/, root-level, or docs/. Use the path as returned from search results.

How to control get_doc ↓

What get_doc does on Project MCP

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

Low Risk

Why get_doc needs a policy

This is a pure read operation that queries and retrieves file content without side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could read sensitive documentation but cannot alter project state or trigger external actions.

From the tool's definition Tool description states 'Get the full content of a specific file' with no modification, deletion, or execution capabilities. It retrieves document content from specified paths (.project/, root-level, or docs/).

Risk signalsAdmin/system-level operation

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

How to control get_doc

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

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

get_doc 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 Project MCP — 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 get_doc

What does the get_doc tool do? +

Get the full content of a specific file. Supports files from .project/, root-level, or docs/. Use the path as returned from search results. It is categorised as a Read tool in the Project MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_doc? +

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

What risk level is get_doc? +

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

Can I rate-limit get_doc? +

Yes. Add a rate_limit block to the get_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.

How do I block get_doc completely? +

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

What MCP server provides get_doc? +

get_doc is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Project MCP tool call.

Start from Project MCP, 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.

42 Project MCP 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.