get_payment_history
AI agents call get_payment_history to retrieve information from Nebulablock without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and 'payment_history' naming convention strongly suggest this tool queries and retrieves payment records without modifying, deleting, or executing operations. Despite the empty description reducing confidence slightly, the naming pattern is unambiguous for a Read operation.
From the tool's definition Tool name 'get_payment_history' indicates retrieval of historical payment data with 'get_' prefix, which is a read operation. The tool description is empty, limiting confirmation.
Attacks that exploit this kind of access
get_payment_history. It is categorised as a Read tool in the Nebulablock MCP Server, which means it retrieves data without modifying state.
Register the Nebulablock MCP server in PolicyLayer and add a rule for get_payment_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 Nebulablock. Nothing to install.
get_payment_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 get_payment_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 get_payment_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.
get_payment_history is provided by the Nebulablock MCP server (nebula-block-data/nebulablock-mcp-server). 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 →