Rename a tag. All notes with this tag will show the new name. Provide either tag_id or current_name.
Part of the Pypi:joplin server.
Free to start. No card required.
AI agents use rename_tag to create or modify resources in Pypi:joplin. 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 rename_tag 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 Pypi:joplin.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"rename_tag": {
"limits": [
{
"counter": "rename_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Pypi:joplin policy for all 32 tools.
These attack patterns abuse exactly the kind of access rename_tag 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.
Rename a tag. All notes with this tag will show the new name. Provide either tag_id or current_name.. It is categorised as a Write tool in the Pypi:joplin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pypi:joplin MCP server in PolicyLayer and add a rule for rename_tag: 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 Pypi:joplin. Nothing to install.
rename_tag 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 rename_tag 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 rename_tag. 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.
rename_tag is provided by the Pypi:joplin MCP server (pypi:joplin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 Pypi:joplin 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.