transfer_credits

transfer_credits

Server Multilead Open API MCP Server vanman2024/multilead-mcp
Category Financial
Risk class Critical
Parameters 00 required

What transfer_credits does on Multilead Open API MCP Server

AI agents use transfer_credits to commit financial operations through Multilead Open API MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why transfer_credits needs a policy

Transferring credits constitutes a financial operation that commits or moves monetary value. Even with an empty description, the name alone strongly indicates a Financial category tool. The blast radius is critical—an AI agent with unrestricted access could drain or redirect credits from an account without explicit user authorization. This ranks above Execute or Write because it directly impacts financial state.

From the tool's definition Tool name 'transfer_credits' indicates movement of financial value (credits) between accounts or entities. Server context confirms this is a lead management and campaign platform where credits likely represent billable resources or currency within the system.

Questions about transfer_credits

What does the transfer_credits tool do? +

transfer_credits. It is categorised as a Financial tool in the Multilead Open API MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_credits? +

Register the Multilead Open API MCP Server 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 Multilead Open API MCP Server. Nothing to install.

What risk level is transfer_credits? +

transfer_credits is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer_credits? +

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.

How do I block transfer_credits completely? +

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.

What MCP server provides transfer_credits? +

transfer_credits is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.