List all relations (foreign keys, M2O, O2M, M2M) in the Directus instance.
AI agents call list_relations 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 queries and retrieves metadata about database relations (foreign keys, M2O, O2M, M2M) without modifying any data or triggering external operations. It is a pure read operation on the Directus schema, similar to inspecting database structure. The blast radius is minimal since it only exposes existing relational structure information.
From the tool's definition Tool name is 'list_relations' and description states it 'List all relations' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all relations (foreign keys, M2O, O2M, M2M) in the Directus instance. 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 list_relations: 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.
list_relations 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_relations 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_relations. 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_relations is provided by the Directus MCP Server MCP server (skeyelab/directus-mcp-server). 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 →