view_workflow_execution_history

View all your execution sessions with a specific workflow.

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/view-workflow-execution-history.md

WHAT IT DOES

What view_workflow_execution_history does on Automagik Tools

AI agents call view_workflow_execution_history 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 view_workflow_execution_history is rated Low

This tool retrieves and displays historical workflow execution data. There is no modification of data, no code execution triggered by the tool itself, no destructive action, and no financial impact. It is a straightforward read/query operation to inspect past workflow sessions.

From the tool's definition Tool name is 'view_workflow_execution_history' and description states 'View all your execution sessions with a specific workflow.' The verb 'view' and action of retrieving/querying historical execution data without modification or side effects classifies this…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

view_workflow_execution_history Allowed

view_workflow_execution_history 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": {
    "view_workflow_execution_history": {}
  }
}

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 view_workflow_execution_history call is checked against it from then on.

FAQ

Questions about view_workflow_execution_history

What does the view_workflow_execution_history tool do? +

View all your execution sessions with a specific workflow. 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 view_workflow_execution_history? +

Register the Automagik Tools MCP server in PolicyLayer and add a rule for view_workflow_execution_history: 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 view_workflow_execution_history? +

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

Can I rate-limit view_workflow_execution_history? +

Yes. Add a rate_limit block to the view_workflow_execution_history 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 view_workflow_execution_history completely? +

Set action: deny in the PolicyLayer policy for view_workflow_execution_history. 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 view_workflow_execution_history? +

view_workflow_execution_history 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

The MCP Attack Database →

Guides

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