AI agents call roadmap_view to retrieve information from Tpm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query and display roadmap data without modifying it. The 'view' suffix strongly suggests a read-only operation. While the description is empty, the naming convention and server context support Read classification.
From the tool's definition Tool name 'roadmap_view' indicates a read operation that retrieves and displays project roadmap information.
Attacks that exploit this kind of access
roadmap_view. It is categorised as a Read tool in the Tpm MCP Server, which means it retrieves data without modifying state.
Register the Tpm MCP server in PolicyLayer and add a rule for roadmap_view: 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 Tpm. Nothing to install.
roadmap_view 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 roadmap_view 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 roadmap_view. 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.
roadmap_view is provided by the Tpm MCP server (urjitbhatia/tpm-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 →