AI agents call list_tags to retrieve information from Sprout 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 message tags associated with a customer account. It has no side effects, does not modify data, does not execute commands, and does not create financial obligations. It fits squarely within the Read category as a data retrieval operation similar to other list/get tools on the server (get_post_analytics, list_profiles, etc.).
From the tool's definition Tool name 'list_tags' and description 'List all message tags for a customer' indicate a retrieval operation with no modification, deletion, or execution of external operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all message tags for a customer. It is categorised as a Read tool in the Sprout MCP Server, which means it retrieves data without modifying state.
Register the Sprout 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 Sprout. 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 Sprout MCP server (jmeserve/sprout-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 →