Create a new goal with name and description. Goals persist across sessions.
AI agents use create_goal to create or update resources in Agent Runtime — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Runtime environment.
Creating a goal is a write operation that adds new data to a persistent store but is reversible (goals can be deleted or modified). While it doesn't directly execute code or delete data, creating goals in an AI task management system could influence downstream agent behavior if goals are vague or malicious.
From the tool's definition Tool description states 'Create a new goal' which is a create operation that generates new persistent data ('Goals persist across sessions'). The tool performs a reversible write operation.
Attacks that exploit this kind of access
Create a new goal with name and description. Goals persist across sessions. It is categorised as a Write tool in the Agent Runtime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Runtime MCP server in PolicyLayer and add a rule for create_goal: 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 Agent Runtime. Nothing to install.
create_goal 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_goal 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_goal. 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_goal is provided by the Agent Runtime MCP server (marc-shade/agent-runtime-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 →