List user-created static classification tags (bounded). System tags (e.g. IoT) not returned.
AI agents call list_static_tags to retrieve information from API-Central 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 static tags without creating, modifying, deleting, or executing any actions. It is bounded retrieval of metadata about network device classification tags. The low severity reflects minimal blast radius—an AI agent misusing this to list tags poses no risk of data loss, unauthorized changes, or unintended operations.
From the tool's definition Tool name 'list_static_tags' and description 'List user-created static classification tags' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a Read operation per the classification rules.
Attacks that exploit this kind of access
List user-created static classification tags (bounded). System tags (e.g. IoT) not returned. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for list_static_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 API-Central. Nothing to install.
list_static_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_static_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_static_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_static_tags is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →