View recent payment history and audit events for a bot.
AI agents call paybot_history to retrieve information from PayBot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and displays payment history and audit events—a non-destructive data retrieval operation. While it operates in a financial context (PayBot payment infrastructure), it performs no financial transactions, code execution, data modification, or destructive actions.
From the tool's definition Tool name 'paybot_history' and description 'View recent payment history and audit events for a bot' indicate a read-only operation that retrieves historical data without modifying, executing, or transferring funds.
Attacks that exploit this kind of access
View recent payment history and audit events for a bot. It is categorised as a Read tool in the PayBot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PayBot MCP Server MCP server in PolicyLayer and add a rule for paybot_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 PayBot MCP Server. Nothing to install.
paybot_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 paybot_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 paybot_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.
paybot_history is provided by the PayBot MCP Server MCP server (rbkunnela/paybot-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 →