legion_list_stories

Proposals newest first, with phase, tally and the inscription each points at.\n\n

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/legion-list-stories.md

WHAT IT DOES

What legion_list_stories does on Aibtc

AI agents call legion_list_stories 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 legion_list_stories is rated Low

This tool retrieves and lists proposal data (sorted by recency, with metadata like phase and tally). It performs a query operation that returns information without creating, modifying, deleting, or executing any side effects.

From the tool's definition Tool name 'legion_list_stories' and description 'Proposals newest first, with phase, tally and the inscription each points at' indicates data retrieval and listing operations with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

legion_list_stories Allowed

legion_list_stories 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": {
    "legion_list_stories": {}
  }
}

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 legion_list_stories call is checked against it from then on.

FAQ

Questions about legion_list_stories

What does the legion_list_stories tool do? +

Proposals newest first, with phase, tally and the inscription each points at.\n\n. 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 legion_list_stories? +

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

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

Can I rate-limit legion_list_stories? +

Yes. Add a rate_limit block to the legion_list_stories 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 legion_list_stories completely? +

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

legion_list_stories 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 369 Aibtc tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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