get_workflow_details

Get detailed information about a specific workflow including its steps and capabilities.

SERVERAutomagik Tools SOURCEnamastexlabs/automagik-tools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/namastexlabs-automagik-tools/get-workflow-details.md

WHAT IT DOES

What get_workflow_details does on Automagik Tools

AI agents call get_workflow_details 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.

RISK

Why get_workflow_details is rated Low

This tool retrieves and queries workflow metadata without side effects. It is a read-only operation that returns information about workflow structure and capabilities, fitting the Read category for data retrieval tools that cause no state changes or external effects.

From the tool's definition Tool name and description indicate retrieval of workflow information: 'Get detailed information about a specific workflow including its steps and capabilities.' No modifications, deletions, or external operations are performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_workflow_details 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_details, this is the rule to start with:

get_workflow_details Allowed

get_workflow_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workflow_details": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every get_workflow_details call is checked against it from then on.

FAQ

Questions about get_workflow_details

What does the get_workflow_details tool do? +

Get detailed information about a specific workflow including its steps and capabilities. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workflow_details? +

Register the Automagik Tools 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 Automagik Tools. Nothing to install.

What risk level is get_workflow_details? +

get_workflow_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workflow_details? +

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.

How do I block get_workflow_details completely? +

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.

What MCP server provides get_workflow_details? +

get_workflow_details 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.

KEEP EXPLORING

More on Automagik Tools, and thousands of servers like it.

This server

All 122 Automagik Tools tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →