Get all execution requests for a specific report type. Returns historical execution records with status and parameters. Production only - not supported in sandbox.
AI agents call payware_data_get_report_requests to retrieve information from Payware 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 queries historical report execution data, which is a Read operation. Severity is medium rather than low because the tool operates in production (not sandbox) and could expose sensitive payment transaction history, merchant financial data, or execution records that could be valuable to an attacker for reconnaissance or compliance violation purposes.
From the tool's definition Tool name contains 'get_report' and description states 'Get all execution requests for a specific report type. Returns historical execution records with status and parameters.' This is a data retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get all execution requests for a specific report type. Returns historical execution records with status and parameters. Production only - not supported in sandbox. It is categorised as a Read tool in the Payware MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_data_get_report_requests: 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 Payware MCP Server. Nothing to install.
payware_data_get_report_requests 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 payware_data_get_report_requests 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 payware_data_get_report_requests. 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.
payware_data_get_report_requests is provided by the Payware MCP Server MCP server (payware/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 →