Set custom passthrough metadata on a ticket. Core ticket fields are protected.
AI agents use storybloq_ticket_meta_set 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.
This tool creates or modifies custom metadata associated with tickets within the project context management system. It is reversible (metadata can be updated again) and non-destructive (protected core fields prevent overwrites of critical data).
From the tool's definition Tool name contains 'set' and description states it modifies metadata on a ticket. The phrase 'Set custom passthrough metadata' indicates a write operation that creates or modifies data.
Documented attack patterns abuse exactly the kind of access storybloq_ticket_meta_set 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_ticket_meta_set:
{
"version": "1",
"default": "deny",
"tools": {
"storybloq_ticket_meta_set": {
"limits": [
{
"counter": "storybloq_ticket_meta_set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}storybloq_ticket_meta_set 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.
Set custom passthrough metadata on a ticket. Core ticket 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_ticket_meta_set: 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_ticket_meta_set 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_ticket_meta_set 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_ticket_meta_set. 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_ticket_meta_set 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.