Unset custom passthrough metadata on an issue. Core issue fields are protected.
AI agents use storybloq_issue_meta_unset to create or update resources in Storybloq — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storybloq environment.
The tool modifies existing issue records by unsetting metadata, which falls under Write (creates or modifies data reversibly). It is not Destructive because: (1) it only removes custom metadata, not the core issue itself; (2) the description explicitly states 'Core issue fields are protected,' indicating limited scope; and (3) unsetting metadata is typically reversible (metadata can be re-added).
From the tool's definition Unset custom passthrough metadata on an issue — this modifies issue data by removing metadata fields, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access storybloq_issue_meta_unset 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_meta_unset:
{
"version": "1",
"default": "deny",
"tools": {
"storybloq_issue_meta_unset": {
"limits": [
{
"counter": "storybloq_issue_meta_unset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}storybloq_issue_meta_unset 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.
Free to start. No card required.
Unset custom passthrough metadata on an issue. Core issue fields are protected. It is categorised as a Write tool in the Storybloq MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Storybloq MCP server in PolicyLayer and add a rule for storybloq_issue_meta_unset: 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_issue_meta_unset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the storybloq_issue_meta_unset 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_issue_meta_unset. 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_issue_meta_unset 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.