Transfer credits to or from a client
AI agents use transfer_credits to commit financial operations through Campaign Monitor MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly manipulates financial account credits, which constitutes a financial transaction. An AI agent with misuse of this tool could transfer credits fraudulently, causing direct financial loss to clients or the company. This is a critical severity risk as it involves irreversible financial obligations and account debits/credits.
From the tool's definition Tool name 'transfer_credits' and description 'Transfer credits to or from a client' explicitly indicate movement of financial resources (credits) between accounts.
Attacks that exploit this kind of access
Transfer credits to or from a client. It is categorised as a Financial tool in the Campaign Monitor MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Campaign Monitor MCP server in PolicyLayer and add a rule for transfer_credits: 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 Campaign Monitor MCP. Nothing to install.
transfer_credits 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 transfer_credits 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 transfer_credits. 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.
transfer_credits is provided by the Campaign Monitor MCP server (pauliowest/cmon-mcp). 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 →