view_workflow_execution_history

THE RISK

Low Risk

Why view_workflow_execution_history needs a policy

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…

Documented attack patterns abuse exactly the kind of access view_workflow_execution_history gives an agent:

POLICY

How to control view_workflow_execution_history

PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for view_workflow_execution_history:

policy.json

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

view_workflow_execution_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Automagik Tools — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Automagik Tools tools

Destructive delete_agent_conversation Delete a conversation session with an agent. This cannot be undone. Destructive delete_credential Delete a stored credential. Destructive delete_message Delete message for everyone. Only works for messages from you (from_me=True), within ~48 h Destructive delete_schedule Delete a schedule. Destructive delete_source Delete a workflow source. Destructive delete_task Delete a task execution. Destructive delete_team_collaboration Delete a team collaboration session. This cannot be undone. Destructive delete_workflow Delete a synchronized workflow.

All 122 Automagik Tools tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

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.

Enforce policy on every Automagik Tools tool call.

Start from Automagik Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →