AI agents call note_get 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.
This tool retrieves existing note content by identifier. It performs a read-only query operation without modifying, deleting, or executing any code. The action is a simple lookup with no irreversible consequences or external effects.
From the tool's definition Tool name 'note_get' and description 'Get full content of a specific note by ID' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
PROJECT MANAGEMENT (TPM): Get full content of a specific note by ID. 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 note_get: 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.
note_get 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 note_get 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 note_get. 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.
note_get 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 →