Transfer ownership of a library to another user.
AI agents use transfer_library to commit financial operations through NASA SciX MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
transfer_library moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
Transfer ownership of a library to another user. It is categorised as a Financial tool in the NASA SciX MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the NASA SciX MCP Server MCP server in PolicyLayer and add a rule for transfer_library: 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 NASA SciX MCP Server. Nothing to install.
transfer_library 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_library 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_library. 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_library is provided by the NASA SciX MCP Server MCP server (thostetler/scix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.