get_run_history

Get execution history for a script

Server MCPMake shex1627/mcpmake
Category Read
Risk class Low
Parameters 00 required

What get_run_history does on MCPMake

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

Why get_run_history needs a policy

This tool queries and retrieves execution history records. It performs a read-only operation that does not create, modify, delete, or execute anything. The action is informational only, with minimal risk if misused by an AI agent.

From the tool's definition Tool name 'get_run_history' and description 'Get execution history for a script' indicate retrieval of historical data with no modification or side effects.

Questions about get_run_history

What does the get_run_history tool do? +

Get execution history for a script. It is categorised as a Read tool in the MCPMake MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_run_history? +

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

What risk level is get_run_history? +

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

Can I rate-limit get_run_history? +

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

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

get_run_history is provided by the MCPMake MCP server (shex1627/mcpmake). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.