Transfers amount of WIP to a recipient to.
AI agents use transfer_wip to commit financial operations through Story SDK MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves cryptocurrency/tokens from one party to another, which constitutes a financial transaction that commits monetary value. Even though the tool description doesn't explicitly state this is irreversible on the application level, token transfers are fundamentally financial operations that transfer value.
From the tool's definition Tool description states it 'Transfers `amount` of WIP to a recipient `to`'. WIP is a token in the Story ecosystem, and the tool directly moves this token between addresses.
Documented attack patterns abuse exactly the kind of access transfer_wip gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Story SDK MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_wip:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_wip": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_wip is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfers amount of WIP to a recipient to. It is categorised as a Financial tool in the Story SDK MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Story SDK MCP Server MCP server in PolicyLayer and add a rule for transfer_wip: 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 Story SDK MCP Server. Nothing to install.
transfer_wip 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_wip 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_wip. 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_wip is provided by the Story SDK MCP Server MCP server (piplabs/story-mcp-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Story SDK MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Story SDK MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.