list_supported_entities
AI agents call list_supported_entities to retrieve information from Mcp Pii Guard Au without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve configuration or metadata about what entities the PII detection system can recognize. It has no side effects and returns information only. The empty description lowers confidence slightly, but the naming pattern and context (sibling tools like detect_pii and sanitize_text are clearly for PII handling) indicate this is an informational query.
From the tool's definition Tool name 'list_supported_entities' indicates a query/listing operation. No description provided, but the name suggests it retrieves a list of supported PII entity types rather than modifying, executing, or deleting data.
Attacks that exploit this kind of access
list_supported_entities. It is categorised as a Read tool in the Mcp Pii Guard Au MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pii Guard Au MCP server in PolicyLayer and add a rule for list_supported_entities: 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 Mcp Pii Guard Au. Nothing to install.
list_supported_entities 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_supported_entities 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_supported_entities. 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_supported_entities is provided by the Mcp Pii Guard Au MCP server (mattwagstaff/mcp-pii-guard-au). 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 →