AI agents call get_stake_info to retrieve information from Logiqical without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain state to retrieve existing staking information. It has no side effects, cannot modify data, and does not execute transactions or move funds. It is a straightforward read operation similar to 'get' or 'fetch' endpoints. Severity is low because misuse merely exposes existing account data without enabling fund movement or destructive actions.
From the tool's definition Tool retrieves staking position data: 'amount staked and pending rewards'. No modifications, deletions, or financial transactions are performed—only data queries.
Attacks that exploit this kind of access
Get staking position: amount staked and pending rewards. It is categorised as a Read tool in the Logiqical MCP Server, which means it retrieves data without modifying state.
Register the Logiqical MCP server in PolicyLayer and add a rule for get_stake_info: 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 Logiqical. Nothing to install.
get_stake_info 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 get_stake_info 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 get_stake_info. 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.
get_stake_info is provided by the Logiqical MCP server (logiqical-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 →