jingswap_get_cycle_state
Get the current Jingswap auction cycle state including phase (deposit/buffer/settle),
This record as markdown: /tools/io-github-aibtcdev-mcp-server/jingswap-get-cycle-state.md
What jingswap_get_cycle_state does on Aibtc
AI agents call jingswap_get_cycle_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 jingswap_get_cycle_state is rated Low
This tool queries and returns data about an auction cycle's current state without modifying anything or triggering side effects. It is a straightforward read operation with minimal security risk.
From the tool's definition Tool name contains 'get' and description indicates it retrieves state information ('Get the current Jingswap auction cycle state'). No modification, execution, or destructive operations are described.
Attacks that exploit this kind of access
The rule that runs jingswap_get_cycle_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 jingswap_get_cycle_state, this is the rule to start with:
jingswap_get_cycle_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 jingswap_get_cycle_state call is checked against it from then on.
Questions about jingswap_get_cycle_state
Get the current Jingswap auction cycle state including phase (deposit/buffer/settle),. 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 jingswap_get_cycle_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.
jingswap_get_cycle_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 jingswap_get_cycle_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 jingswap_get_cycle_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.
jingswap_get_cycle_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