Get a single operation by ID from Directus. Optionally specify fields to return and metadata options.
AI agents call get_operation 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 existing operation metadata from Directus without modifying, deleting, or executing any operations. It is a straightforward query operation that returns data about a stored operation. No data is created, modified, deleted, or executed as a result of using this tool. The severity is low because retrieving operation metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states 'Get a single operation by ID from Directus' with options to 'specify fields to return and metadata options'.
Attacks that exploit this kind of access
Get a single operation by ID from Directus. Optionally specify fields to return and metadata options. 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 get_operation: 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.
get_operation 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 get_operation 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 get_operation. 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.
get_operation 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 →