reject_payouts
AI agents use reject_payouts to create or update resources in Fuul MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fuul MCP Server environment.
This tool modifies the status of existing payout records (rejecting them), which is a reversible Write operation. It does not permanently delete data (which would be Destructive) or move money (Financial—it prevents/blocks payouts rather than executing transfers).
From the tool's definition Tool name 'reject_payouts' indicates modification of payout records. The empty description limits confidence, but in the context of a payout management system, rejection implies state change (marking payouts as rejected) rather than deletion.
Attacks that exploit this kind of access
reject_payouts. It is categorised as a Write tool in the Fuul MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fuul MCP Server MCP server in PolicyLayer and add a rule for reject_payouts: 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.
reject_payouts is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reject_payouts 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 reject_payouts. 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.
reject_payouts 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 →