update_payout_term
AI agents use update_payout_term to commit financial operations through Fuul MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool name strongly implies modification of payout terms (e.g., payment schedules, amounts, conditions) within a financial payout system. Changes to payout terms can directly affect financial obligations and money movement, placing this in the Financial category. Confidence is reduced due to the empty description, but the server context and sibling tools (approve_payouts) make financial impact highly likely.
From the tool's definition Tool name 'update_payout_term' on a server that 'Manages affiliate programs, analytics, incentives, and payouts'; sibling tool 'approve_payouts' confirms financial payout context.
Attacks that exploit this kind of access
update_payout_term. It is categorised as a Financial tool in the Fuul MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Fuul MCP Server MCP server in PolicyLayer and add a rule for update_payout_term: 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.
update_payout_term is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the update_payout_term 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 update_payout_term. 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.
update_payout_term 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 →