AI agents use create_pbi to create or update resources in Vacklogen — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vacklogen environment.
This tool creates new Product Backlog Item (PBI) entries, which is a data modification operation. It is reversible (can be deleted) and has a bounded scope (adding to a specific project), making it Write category rather than Execute or Destructive. Severity is medium because creating unwanted PBIs could clutter a project backlog and require cleanup, but the impact is contained and reversible.
From the tool's definition Tool name 'create_pbi' and description 'Add a new PBI as a stub to an existing project' indicate creation of new data.
Attacks that exploit this kind of access
Add a new PBI as a stub to an existing project. It is categorised as a Write tool in the Vacklogen MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vacklogen MCP server in PolicyLayer and add a rule for create_pbi: 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 Vacklogen. Nothing to install.
create_pbi 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 create_pbi 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 create_pbi. 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.
create_pbi is provided by the Vacklogen MCP server (vacklogen-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →