Call this when the user wants to track a new task, add an action item, create a follow-up, or log a to-do. IMPORTANT: Maximum 10 actions per batch. If creating more, ask for confirmation first, then batch with pauses. If the user has multiple meetings, call list_meetings first and ask which meeti...
Risk signalsHigh parameter count (12 properties)
Part of the Gantta server.
Free to start. No card required.
AI agents use create_action to create or modify resources in Gantta. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_action repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Gantta.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"create_action": {
"limits": [
{
"counter": "create_action_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Gantta policy for all 26 tools.
These attack patterns abuse exactly the kind of access create_action gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Call this when the user wants to track a new task, add an action item, create a follow-up, or log a to-do. IMPORTANT: Maximum 10 actions per batch. If creating more, ask for confirmation first, then batch with pauses. If the user has multiple meetings, call list_meetings first and ask which meeting these actions relate to — then pass that meeting_id. If no meeting context, omit meeting_id (a container will be auto-created).. It is categorised as a Write tool in the Gantta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gantta MCP server in PolicyLayer and add a rule for create_action: 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 Gantta. Nothing to install.
create_action 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_action 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_action. 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_action is provided by the Gantta MCP server (gantta/gantta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Gantta tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.