Low Risk

get_type_info

get_type_info

How to control get_type_info ↓

What get_type_info does on Rust Docs MCP Server

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

Low Risk

Why get_type_info needs a policy

This tool retrieves type information from Rust documentation—a read-only operation with no side effects. It fits the pattern of documentation access tools on this server. Even with an empty description, the tool name and server context indicate data retrieval without modification, deletion, or execution capabilities.

From the tool's definition Tool name 'get_type_info' combined with server purpose (Rust documentation access from docs.rs) and sibling tools (get_crate_documentation, get_crate_versions, get_feature_flags, get_source_code, search_crates, search_symbols) all perform read-only queries.

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

How to control get_type_info

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

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

get_type_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 Rust Docs MCP Server — 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_type_info

What does the get_type_info tool do? +

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

How do I enforce a policy on get_type_info? +

Register the Rust Docs MCP Server MCP server in PolicyLayer and add a rule for get_type_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 Rust Docs MCP Server. Nothing to install.

What risk level is get_type_info? +

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

Can I rate-limit get_type_info? +

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

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

get_type_info is provided by the Rust Docs MCP Server MCP server (laptou/rust-docs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Rust Docs MCP Server tool call.

Start from Rust Docs MCP Server, 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.

7 Rust Docs MCP Server 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.