zabbix_get_script_execution_history

THE RISK

Low Risk

Why zabbix_get_script_execution_history needs a policy

This tool queries and retrieves already-recorded script execution history. It performs a read-only lookup operation on existing Zabbix event data. There are no side effects, no data is modified, and no new operations are triggered. The blast radius of misuse is minimal—an attacker gains only visibility into past script activities.

From the tool's definition Tool name contains 'get_' and description states 'Get history of script executions from Zabbix events' — purely retrieves historical data with no modifications, creations, deletions, or execution of new scripts.

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

POLICY

How to control zabbix_get_script_execution_history

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

policy.json

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

zabbix_get_script_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 Zabbix MCP Server — 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 Zabbix MCP Server tools

Destructive zabbix_delete_actions Delete actions from Zabbix Destructive zabbix_delete_correlations Delete event correlations from Zabbix Destructive zabbix_delete_dashboards Delete dashboards from Zabbix Destructive zabbix_delete_discovery_rules Delete Low-Level Discovery (LLD) rules from Zabbix Destructive zabbix_delete_hostgroups Delete host groups from Zabbix Destructive zabbix_delete_icon_maps Delete icon maps from Zabbix Destructive zabbix_delete_items Delete items from Zabbix Destructive zabbix_delete_maintenance Delete maintenance periods from Zabbix

All 102 Zabbix MCP Server 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 zabbix_get_script_execution_history

What does the zabbix_get_script_execution_history tool do? +

Get history of script executions from Zabbix events. It is categorised as a Read tool in the Zabbix MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zabbix_get_script_execution_history? +

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

What risk level is zabbix_get_script_execution_history? +

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

Can I rate-limit zabbix_get_script_execution_history? +

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

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

zabbix_get_script_execution_history is provided by the Zabbix MCP Server MCP server (leroylim/zabbix-mcp-server-nodejs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zabbix MCP Server tool call.

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

CHECK YOUR STACK →