AI agents use add_task to create or update resources in XiaozhiMCP-MapNAVI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your XiaozhiMCP-MapNAVI environment.
The tool creates or modifies task records based on its name. Without an explicit description, confidence is moderate. The action is reversible (tasks can be deleted or modified later) and does not irreversibly destroy data or move money. The blast radius is medium: a compromised agent could create unwanted tasks within the mapped system, but impact is limited to task records.
From the tool's definition Tool named 'add_task' with empty description; sibling tools include 'get_tasks', 'complete_task', and 'plan_driving_route' suggesting a task management system. The name 'add_task' indicates data creation/modification.
Documented attack patterns abuse exactly the kind of access add_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XiaozhiMCP-MapNAVI, and nothing reaches the server without passing your rules. This is the rule we recommend for add_task:
{
"version": "1",
"default": "deny",
"tools": {
"add_task": {
"limits": [
{
"counter": "add_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_task 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.
Free to start. No card required.
add_task. It is categorised as a Write tool in the XiaozhiMCP-MapNAVI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the XiaozhiMCP-MapNAVI MCP server in PolicyLayer and add a rule for add_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 XiaozhiMCP-MapNAVI. Nothing to install.
add_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 add_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 add_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.
add_task is provided by the XiaozhiMCP-MapNAVI MCP server (rickeylaiii/xiaoai_mapmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from XiaozhiMCP-MapNAVI, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 XiaozhiMCP-MapNAVI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.