Low Risk

storybloq_issue_list

List issues with optional filters

How to control storybloq_issue_list ↓

AI agents call storybloq_issue_list to retrieve information from Storybloq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves a list of issues with optional filtering criteria. It only reads/queries data from the .story/ directory without creating, modifying, or deleting anything.

From the tool's definition List issues with optional filters

Documented attack patterns abuse exactly the kind of access storybloq_issue_list gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Storybloq, and nothing reaches the server without passing your rules. This is the rule we recommend for storybloq_issue_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "storybloq_issue_list": {}
  }
}

storybloq_issue_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Storybloq — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the storybloq_issue_list tool do? +

List issues with optional filters. It is categorised as a Read tool in the Storybloq MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on storybloq_issue_list? +

Register the Storybloq MCP server in PolicyLayer and add a rule for storybloq_issue_list: 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 Storybloq. Nothing to install.

What risk level is storybloq_issue_list? +

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

Can I rate-limit storybloq_issue_list? +

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

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

storybloq_issue_list is provided by the Storybloq MCP server (storybloq/storybloq). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Storybloq tool call.

Deterministic rules across all 54 Storybloq tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

54 Storybloq tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.