Get workflow details including jobPayloadSchema that defines required inputs for a workflow
AI agents call get_workflow_details to retrieve information from Opus 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 queries workflow metadata and schema information without creating, modifying, executing, deleting, or moving any data. It is purely informational and presents no risk of unintended side effects when invoked by an AI agent. The blast radius is minimal as it only exposes existing workflow definitions.
From the tool's definition The tool name is 'get_workflow_details' and the description states it retrieves workflow details and job payload schema definitions. The verb 'Get' and the retrieval nature of querying workflow metadata indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
Get workflow details including jobPayloadSchema that defines required inputs for a workflow. It is categorised as a Read tool in the Opus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Opus MCP Server MCP server in PolicyLayer and add a rule for get_workflow_details: 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 Opus MCP Server. Nothing to install.
get_workflow_details 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_workflow_details 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_workflow_details. 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_workflow_details is provided by the Opus MCP Server MCP server (moenamatics/opus-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 →