Пополнить брокерский счёт с банковского в Т-Инвестициях
AI agents use pay_in to commit financial operations through T-Invest MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money between financial accounts (bank to brokerage), which constitutes a financial transaction that commits monetary value. The ability to transfer funds without proper authorization or through agent misuse could result in unauthorized fund transfers.
From the tool's definition Tool name 'pay_in' combined with description 'Пополнить брокерский счёт с банковского в Т-Инвестициях' (Replenish brokerage account from bank account in T-Investments) explicitly transfers funds from a bank account to an investment brokerage account.
Attacks that exploit this kind of access
Пополнить брокерский счёт с банковского в Т-Инвестициях. It is categorised as a Financial tool in the T-Invest MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the T-Invest MCP Server MCP server in PolicyLayer and add a rule for pay_in: 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 T-Invest MCP Server. Nothing to install.
pay_in 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 pay_in 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 pay_in. 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.
pay_in is provided by the T-Invest MCP Server MCP server (nonnname/t-invest-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 →