addTask
Add a new task to the task list. Returns the newly created task.
This record as markdown: /tools/firebase-genkit/addtask.md
What addTask does on Genkit MCP
AI agents use addTask to create or update resources in Genkit MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genkit MCP environment.
Why addTask is rated Medium
This tool creates new data (a task) in a reversible manner. It does not execute arbitrary code, delete data, or have financial implications. The impact is limited to task list state. Severity is low because misuse would only create unwanted tasks, which are easily removable and have minimal blast radius.
From the tool's definition Tool name 'addTask' and description 'Add a new task to the task list' indicates creation of new data. The phrase 'Returns the newly created task' confirms data is being written/persisted.
Attacks that exploit this kind of access
The rule that runs addTask safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genkit MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For addTask, this is the rule to start with:
addTask 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Genkit MCP, apply this rule, and every addTask call is checked against it from then on.
Questions about addTask
Add a new task to the task list. Returns the newly created task. It is categorised as a Write tool in the Genkit MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Genkit MCP server in PolicyLayer and add a rule for addTask: 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 Genkit MCP. Nothing to install.
addTask 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 addTask 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 addTask. 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.
addTask is provided by the Genkit MCP server (genkit-ai/genkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genkit, and thousands of servers like it.
This server
Across the catalogue