list_payouts_pending_approval
AI agents call list_payouts_pending_approval to retrieve information from Fuul MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name clearly indicates a read operation that retrieves pending payout data. While the domain involves financial payouts, this tool itself only queries/lists status without moving money or creating financial obligations.
From the tool's definition Tool name is 'list_payouts_pending_approval' which retrieves/queries a list of pending payouts for review. The verb 'list' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
list_payouts_pending_approval. It is categorised as a Read tool in the Fuul MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fuul MCP Server MCP server in PolicyLayer and add a rule for list_payouts_pending_approval: 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 Fuul MCP Server. Nothing to install.
list_payouts_pending_approval 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 list_payouts_pending_approval 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 list_payouts_pending_approval. 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.
list_payouts_pending_approval is provided by the Fuul MCP Server MCP server (kuyen-labs/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 →