AI agents use eth_stake_tokens to commit financial operations through PortalMCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Staking tokens moves financial assets into a smart contract, locking them up and committing them to a DeFi financial operation. This constitutes a financial commitment that is difficult or impossible to reverse depending on the staking contract terms. The server description explicitly lists 'DeFi operations' as a supported use case.
From the tool's definition 'stake tokens in a staking contract' — staking commits tokens to a financial smart contract, locking up assets and creating financial obligations/positions on the Ethereum blockchain
Attacks that exploit this kind of access
Prepare a transaction to stake tokens in a staking contract. It is categorised as a Financial tool in the PortalMCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Portal MCP server in PolicyLayer and add a rule for eth_stake_tokens: 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 PortalMCP. Nothing to install.
eth_stake_tokens 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 eth_stake_tokens 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 eth_stake_tokens. 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.
eth_stake_tokens is provided by the Portal MCP server (portalfnd/portalmcp). 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 →