This record as markdown: /tools/io-github-bitgett-q402-mcp/q402-stake-positions.md
What q402_stake_positions does on Q402 Mcp
AI agents call q402_stake_positions to retrieve information from Q402 Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why q402_stake_positions is rated Low
This is a read-only operation that displays stake positions and wallet information without modifying, executing, or transferring any assets. The explicit 'READ-ONLY' designation confirms it is a query operation with no capability to mutate state or commit financial transactions.
From the tool's definition Tool name 'q402_stake_positions' combined with description 'READ-ONLY - show the Agent Wallet' explicitly indicates retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs q402_stake_positions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Q402 Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For q402_stake_positions, this is the rule to start with:
q402_stake_positions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Q402 Mcp, apply this rule, and every q402_stake_positions call is checked against it from then on.
Questions about q402_stake_positions
READ-ONLY - show the Agent Wallet. It is categorised as a Read tool in the Q402 Mcp MCP Server, which means it retrieves data without modifying state.
Register the Q402 MCP server in PolicyLayer and add a rule for q402_stake_positions: 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 Q402 Mcp. Nothing to install.
q402_stake_positions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the q402_stake_positions 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 q402_stake_positions. 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.
q402_stake_positions is provided by the Q402 MCP server (@quackai/q402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Q402, and thousands of servers like it.
This server
Across the catalogue