list_stacking_signers

List PoX-5 signer managers in the signer set for a reward cycle (default: next cycle), with

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/list-stacking-signers.md

WHAT IT DOES

What list_stacking_signers does on Aibtc

AI agents call list_stacking_signers 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.

RISK

Why list_stacking_signers is rated Low

Queries stacking signer data without modifying state or causing effects.

From the tool's definition List PoX-5 signer managers in signer set for reward cycle

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_stacking_signers 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 list_stacking_signers, this is the rule to start with:

list_stacking_signers Allowed

list_stacking_signers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_stacking_signers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every list_stacking_signers call is checked against it from then on.

FAQ

Questions about list_stacking_signers

What does the list_stacking_signers tool do? +

List PoX-5 signer managers in the signer set for a reward cycle (default: next cycle), with. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_stacking_signers? +

Register the Aibtc MCP server in PolicyLayer and add a rule for list_stacking_signers: 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.

What risk level is list_stacking_signers? +

list_stacking_signers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_stacking_signers? +

Yes. Add a rate_limit block to the list_stacking_signers 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.

How do I block list_stacking_signers completely? +

Set action: deny in the PolicyLayer policy for list_stacking_signers. 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.

What MCP server provides list_stacking_signers? +

list_stacking_signers 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 366 Aibtc tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →