Diagnose collection access issues and permissions
AI agents call diagnose_collection_access to retrieve information from Directus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and queries the state of collection access and permissions to identify issues. It retrieves information about access control without creating, modifying, deleting, executing external operations, or committing financial transactions.
From the tool's definition Tool name and description indicate diagnostic and permission checking functionality: 'diagnose collection access issues and permissions'. The verb 'diagnose' implies inspection and analysis of existing state, not modification or execution of operations.
Attacks that exploit this kind of access
Diagnose collection access issues and permissions. It is categorised as a Read tool in the Directus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Directus MCP Server MCP server in PolicyLayer and add a rule for diagnose_collection_access: 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 Directus MCP Server. Nothing to install.
diagnose_collection_access 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 diagnose_collection_access 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 diagnose_collection_access. 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.
diagnose_collection_access is provided by the Directus MCP Server MCP server (staminna/mcp-server-claude). 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 →