Get list of PoX cycles with stacking information
AI agents call get_pox_cycles to retrieve information from Stacks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists PoX (Proof of Transfer) cycle data and stacking information. The verb 'Get' and the informational nature of the data (listing cycles with metadata) confirm this is a read-only operation. It has no side effects, cannot modify blockchain state, and poses minimal risk if misused by an AI agent—the worst outcome would be retrieving stale or unnecessary data.
From the tool's definition Tool name 'get_pox_cycles' and description 'Get list of PoX cycles with stacking information' indicate a data retrieval operation that queries existing stacking cycle information without modifying state.
Attacks that exploit this kind of access
Get list of PoX cycles with stacking information. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for get_pox_cycles: 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 Stacks AI MCP Server. Nothing to install.
get_pox_cycles 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_pox_cycles 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_pox_cycles. 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_pox_cycles is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-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 →