AI agents call listTags to retrieve information from Memnote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing tags without creating, modifying, deleting, or executing any operations. It is a straightforward read/retrieve operation with minimal risk exposure.
From the tool's definition "List tags" and "Returns all non-deleted tags for the authenticated user." - a retrieval operation with no side effects.
Attacks that exploit this kind of access
List tags Returns all non-deleted tags for the authenticated user. It is categorised as a Read tool in the Memnote MCP Server, which means it retrieves data without modifying state.
Register the Memnote MCP server in PolicyLayer and add a rule for listTags: 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 Memnote. Nothing to install.
listTags 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 listTags 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 listTags. 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.
listTags is provided by the Memnote MCP server (@randomfact/memnote-mcp-server). 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 →