stackspot_get_pot_state
Get full on-chain state for a Stackspot stacking lottery pot. Returns the pot value, lock status, configurations, pool config, and detailed state. Use a bare contract name (e.g.,
This record as markdown: /tools/io-github-aibtcdev-mcp-server/stackspot-get-pot-state.md
What stackspot_get_pot_state does on Aibtc
AI agents call stackspot_get_pot_state to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stackspot_get_pot_state is rated Low
This tool retrieves and queries blockchain state information about a Stackspot stacking lottery pot. It has no capability to modify, delete, execute commands, or move funds. The operation is read-only with no side effects, making it a standard Read category tool with low severity risk.
From the tool's definition Tool description explicitly states 'Get full on-chain state' and 'Returns the pot value, lock status, configurations, pool config, and detailed state.' The verb 'Get' and the action of retrieving on-chain state data without modification indicates a read-only…
Attacks that exploit this kind of access
The rule that runs stackspot_get_pot_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stackspot_get_pot_state, this is the rule to start with:
stackspot_get_pot_state 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 Aibtc, apply this rule, and every stackspot_get_pot_state call is checked against it from then on.
Questions about stackspot_get_pot_state
Get full on-chain state for a Stackspot stacking lottery pot. Returns the pot value, lock status, configurations, pool config, and detailed state. Use a bare contract name (e.g.,. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for stackspot_get_pot_state: 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 Aibtc. Nothing to install.
stackspot_get_pot_state 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 stackspot_get_pot_state 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 stackspot_get_pot_state. 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.
stackspot_get_pot_state is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue