Integration smoke test — creates, updates, and deletes test entities to verify the full pipeline
AI agents call storybloq_selftest to permanently remove resources in Storybloq — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly performs deletions as part of its smoke test routine. Even though the deleted entities are test entities, deletion is irreversible, placing this in the Destructive category. The blast radius is medium since it operates on test data within the structured .story/ directory, but could inadvertently affect real project context if not properly isolated.
From the tool's definition creates, updates, and deletes test entities to verify the full pipeline
Documented attack patterns abuse exactly the kind of access storybloq_selftest 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_selftest:
{
"version": "1",
"default": "deny",
"hide": [
"storybloq_selftest"
]
}storybloq_selftest disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Integration smoke test — creates, updates, and deletes test entities to verify the full pipeline. It is categorised as a Destructive tool in the Storybloq MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Storybloq MCP server in PolicyLayer and add a rule for storybloq_selftest: 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.
storybloq_selftest is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the storybloq_selftest 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 storybloq_selftest. 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.
storybloq_selftest 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.
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.