Use to add CRM tags to the verified customer for booking workflow tracking.
Part of the TaskMan of London server.
Free to start. No card required.
AI agents use tag_contact to create or modify resources in TaskMan of London. 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 tag_contact 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 TaskMan of London.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"tag_contact": {
"limits": [
{
"counter": "tag_contact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full TaskMan of London policy for all 20 tools.
These attack patterns abuse exactly the kind of access tag_contact 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.
Use to add CRM tags to the verified customer for booking workflow tracking.. It is categorised as a Write tool in the TaskMan of London MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TaskMan of London MCP server in PolicyLayer and add a rule for tag_contact: 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 TaskMan of London. Nothing to install.
tag_contact 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 tag_contact 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 tag_contact. 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.
tag_contact is provided by the TaskMan of London MCP server (https://taskman.london/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 TaskMan of London 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.