get_history

get_history

Server Keshro MCP jlewitt1/keshro-mcp
Category Read
Risk class Low
Parameters 00 required

What get_history does on Keshro MCP

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

Why get_history needs a policy

The tool name strongly suggests querying or fetching historical records (typical Read operation pattern). No description is available to suggest side effects, modifications, or destructive capabilities.

From the tool's definition Tool name 'get_history' indicates retrieval of historical data with no description provided. Based on naming convention and context within a project management/execution layer, this retrieves past records without modifying, deleting, or executing operations.

Questions about get_history

What does the get_history tool do? +

get_history. It is categorised as a Read tool in the Keshro MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_history? +

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

What risk level is get_history? +

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

Can I rate-limit get_history? +

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

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

get_history is provided by the Keshro MCP server (jlewitt1/keshro-mcp). 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.