get_execution_request
AI agents call get_execution_request to retrieve information from Morpheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests a read operation that queries or retrieves an execution request object without modifying state. No destructive, write, or execution capabilities are implied by the name alone. Since the description is empty, confidence is moderate rather than high. If this tool returned request data for informational purposes only, it represents a Read operation with minimal blast radius.
From the tool's definition Tool name 'get_execution_request' uses 'get' prefix, which typically retrieves data. The description is empty, limiting certainty.
Attacks that exploit this kind of access
get_execution_request. It is categorised as a Read tool in the Morpheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for get_execution_request: 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 Morpheus MCP Server. Nothing to install.
get_execution_request 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_execution_request 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_execution_request. 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_execution_request is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). 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 →