Query items from a collection with advanced filtering, sorting, pagination, and search. Supports Directus filter operators like _eq, _neq, _lt, _lte, _gt, _gte, _in, _nin, _null, _nnull, _contains, _ncontains, _starts_with, _nstarts_with, _ends_with, _nends_with, _between, _nbetween. Example: {co...
AI agents call query_items 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 retrieves and filters data from a Directus collection without modifying, deleting, or executing code. It is a pure read operation with no side effects. The blast radius of misuse is minimal—an agent could over-query or retrieve sensitive data it shouldn't access, but cannot alter or destroy it. Low severity reflects the informational nature of the operation.
From the tool's definition Tool description states 'Query items from a collection with advanced filtering, sorting, pagination, and search.' The supported operators (_eq, _neq, _lt, _gt, _in, _contains, _starts_with, etc.) are all read-only query filters with no mutation capabilities.
Attacks that exploit this kind of access
Query items from a collection with advanced filtering, sorting, pagination, and search. Supports Directus filter operators like _eq, _neq, _lt, _lte, _gt, _gte, _in, _nin, _null, _nnull, _contains, _ncontains, _starts_with, _nstarts_with, _ends_with, _nends_with, _between, _nbetween. Example: {collection:. 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 query_items: 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.
query_items 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 query_items 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 query_items. 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.
query_items 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 →