AI agents use create_checklist to create or update resources in Yo Bug — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yo Bug environment.
An AI agent can call create_checklist faster than any human can review — one bad instruction and it creates or modifies resources in Yo Bug by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Create a test checklist with GROUPED TEST CASES and push it to the user. It is categorised as a Write tool in the Yo Bug MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yo Bug MCP server in PolicyLayer and add a rule for create_checklist: 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 Yo Bug. Nothing to install.
create_checklist 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_checklist 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_checklist. 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_checklist is provided by the Yo Bug MCP server (wyykerwin/yo-bug). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.