Call once to register the user's birth date/time/gender. Each call is a complete replacement — all 6 fields must be supplied. For fields the user does not know or prefers not to share, pass null explicitly (e.g. hour: null for unknown birth time, gender: null for unspecified). To update just one ...
Part of the Intentions MCP Server server.
Free to start. No card required.
AI agents use intentions_set_birth_info to create or modify resources in Intentions MCP Server. 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 intentions_set_birth_info 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 Intentions MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"intentions_set_birth_info": {
"limits": [
{
"counter": "intentions_set_birth_info_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Intentions MCP Server policy for all 7 tools.
These attack patterns abuse exactly the kind of access intentions_set_birth_info 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 once to register the user's birth date/time/gender. Each call is a complete replacement — all 6 fields must be supplied. For fields the user does not know or prefers not to share, pass null explicitly (e.g. hour: null for unknown birth time, gender: null for unspecified). To update just one field, first call intentions_get_profile to fetch the current values, merge the user's new input, then call this tool with the full merged payload. Identity-changing edits (year/month/day/hour/gender) are limited to 3 per calendar month; adding precision (e.g. filling in a previously-null hour) is always free. Returns the element profile.. It is categorised as a Write tool in the Intentions MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intentions MCP Server MCP server in PolicyLayer and add a rule for intentions_set_birth_info: 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 Intentions MCP Server. Nothing to install.
intentions_set_birth_info 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 intentions_set_birth_info 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 intentions_set_birth_info. 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.
intentions_set_birth_info is provided by the Intentions MCP Server MCP server (https://mcp.intentions.me/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Intentions MCP Server 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.