get_workflow
Get detailed information about a specific workflow.
This record as markdown: /tools/namastexlabs-automagik-tools/get-workflow.md
What get_workflow does on Automagik Tools
AI agents call get_workflow to retrieve information from Automagik Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_workflow is rated Low
This tool retrieves and queries workflow metadata without any side effects. It follows the Read category pattern (get, fetch, retrieve) and poses minimal risk if misused by an agent, as it only returns information about existing workflows without creating, modifying, executing, or deleting anything.
From the tool's definition Tool name is 'get_workflow' and description states 'Get detailed information about a specific workflow' — a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs get_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_workflow, this is the rule to start with:
get_workflow is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every get_workflow call is checked against it from then on.
Questions about get_workflow
Get detailed information about a specific workflow. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for get_workflow: 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 Automagik Tools. Nothing to install.
get_workflow 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 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. 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 is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Automagik Tools, and thousands of servers like it.
This server
Across the catalogue