View your recent prompts and execution results.
AI agents call history to retrieve information from RespCode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays previously stored prompts and execution results. It is purely informational—reading historical records without creating, modifying, deleting, or executing any code. The blast radius is minimal, as the worst outcome would be information disclosure of the user's own prior activities.
From the tool's definition Tool name 'history' and description 'View your recent prompts and execution results' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
View your recent prompts and execution results. It is categorised as a Read tool in the RespCode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RespCode MCP Server MCP server in PolicyLayer and add a rule for 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 RespCode MCP Server. Nothing to install.
history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
history is provided by the RespCode MCP Server MCP server (respcodeai/respcode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →