Call this ONLY after you have asked the user all three questions (name, role, project details) one at a time and received their answers. Do NOT call this with assumed or default values. Every field must come from the user's actual response. This personalizes their workspace and stores project con...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Gantta server.
Free to start. No card required.
AI agents use complete_onboarding 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 complete_onboarding 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": {
"complete_onboarding": {
"limits": [
{
"counter": "complete_onboarding_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 complete_onboarding 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 ONLY after you have asked the user all three questions (name, role, project details) one at a time and received their answers. Do NOT call this with assumed or default values. Every field must come from the user's actual response. This personalizes their workspace and stores project context for all future conversations.. 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 complete_onboarding: 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.
complete_onboarding 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 complete_onboarding 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 complete_onboarding. 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.
complete_onboarding 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.