Create a task. due = ISO-8601 datetime. project stored in source column.
AI agents use create_task to create or update resources in Nexus Core — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus Core environment.
The tool creates or modifies data (a task record) in a reversible manner. It does not delete, execute code, trigger external operations, or move money. The operation is straightforward task creation with metadata (due date, project). Severity is low because misuse would only create unwanted task records, which are easily deletable and pose minimal risk to the system or user.
From the tool's definition Tool description states 'Create a task' with parameters for due date and project source—this is a data creation operation with no side effects beyond adding a record to a task management system.
Attacks that exploit this kind of access
Create a task. due = ISO-8601 datetime. project stored in source column. It is categorised as a Write tool in the Nexus Core MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nexus Core MCP server in PolicyLayer and add a rule for create_task: 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 Nexus Core. Nothing to install.
create_task 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_task 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_task. 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_task is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →