shard_to_story · Proofhub MCP: Risk & Policy

WHAT IT DOES

What shard_to_story does on Proofhub

AI agents use shard_to_story to create or update resources in Proofhub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proofhub environment.

WHY IT NEEDS A POLICY

Why shard_to_story needs a policy

The tool writes/creates a new story file on disk (or storage) containing structured content derived from a ProofHub task. This is a write/create operation producing a new artifact. It does not execute code, delete data, or move money. The blast radius is moderate — a misuse could create misleading or incorrect story files that misdirect a dev agent, but it is reversible.

From the tool's definition "shard a ProofHub task into a self-contained story file" — creates a new file artifact from task data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shard_to_story Rate-limited

shard_to_story stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "shard_to_story": {
      "limits": [
        {
          "counter": "shard_to_story_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Proofhub, so you can run agents against it safely.

FAQ

Questions about shard_to_story

What does the shard_to_story tool do? +

BMAD: shard a ProofHub task into a self-contained story file (Context / Acceptance Criteria / Dev Notes / Tasks) a dev agent can act on without re-opening the ticket. Includes a suggested role + tier. project and todolist default to context. It is categorised as a Write tool in the Proofhub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on shard_to_story? +

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

What risk level is shard_to_story? +

shard_to_story is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit shard_to_story? +

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

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

shard_to_story is provided by the Proofhub MCP server (yashmody/proofhub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.