list_automation_history

Execution log showing what triggered, what actions ran, and success/failure status.

SERVERBusinys SOURCE@businys/mcp-server

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/app-businys-mcp-server/list-automation-history.md

WHAT IT DOES

What list_automation_history does on Businys

AI agents call list_automation_history to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_automation_history is rated Low

This tool retrieves and displays historical automation execution records. It performs a query-like operation to fetch past event logs, their triggers, executed actions, and outcomes. No data is created, modified, deleted, or executed by this tool itself—it only reads existing log entries.

From the tool's definition Tool name 'list_automation_history' and description 'Execution log showing what triggered, what actions ran, and success/failure status' indicates retrieval of historical log data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_automation_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_automation_history, this is the rule to start with:

list_automation_history Allowed

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

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

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

FAQ

Questions about list_automation_history

What does the list_automation_history tool do? +

Execution log showing what triggered, what actions ran, and success/failure status. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_automation_history? +

Register the Businys MCP server in PolicyLayer and add a rule for list_automation_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 Businys. Nothing to install.

What risk level is list_automation_history? +

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

Can I rate-limit list_automation_history? +

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

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

list_automation_history is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Businys, and thousands of servers like it.

This server

All 248 Businys tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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