Low Risk

get_project_info

Get information about the project structure and files

How to control get_project_info ↓

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

Low Risk

This tool retrieves or queries project metadata and structure information without any side effects, modifications, or destructive actions. It is a read-only operation consistent with the 'Read' category (list, get, fetch). The low severity reflects minimal blast radius—an agent misusing this can only over-retrieve or leak information about project structure, not modify or delete data.

From the tool's definition Tool name 'get_project_info' and description 'Get information about the project structure and files' indicate a retrieval operation with no modification capability.

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

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

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

get_project_info 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 Mcp Rtfm — 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.

Go deeper

What does the get_project_info tool do? +

Get information about the project structure and files. It is categorised as a Read tool in the Mcp Rtfm MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_project_info? +

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

What risk level is get_project_info? +

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

Can I rate-limit get_project_info? +

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

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

get_project_info is provided by the Mcp Rtfm MCP server (ryanjoachim/mcp-rtfm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Rtfm tool call.

Deterministic rules across all 11 Mcp Rtfm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

11 Mcp Rtfm tools catalogued and risk-classified — across an index of 42,500+ 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.