list_tags
AI agents call list_tags to retrieve information from Prompt Store MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists tags from the prompt library without modifying data. It has no side effects and fits the Read category (retrieve/query operations). Severity is low because the blast radius of misuse is minimal—an agent can only enumerate existing tags, which represents no data loss, financial impact, or unauthorized modification risk. The local-only nature of the server further constrains risk exposure.
From the tool's definition Tool name is 'list_tags' which indicates a listing/retrieval operation. No description provided, but the naming pattern aligns with sibling tools like 'list_prompts' and 'filter_by_tags' which are query operations on the prompt store.
Attacks that exploit this kind of access
list_tags. It is categorised as a Read tool in the Prompt Store MCP MCP Server, which means it retrieves data without modifying state.
Register the Prompt Store MCP server in PolicyLayer and add a rule for list_tags: 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 Prompt Store MCP. Nothing to install.
list_tags 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 list_tags 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 list_tags. 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.
list_tags is provided by the Prompt Store MCP server (mhoshdev/prompt-store-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 →