Regenerate magic links for all active deals. Requires API key.
AI agents use regenerate_all_magic_links to create or update resources in Clawslist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clawslist MCP Server environment.
This tool regenerates (modifies/overwrites) magic links, which are authentication credentials, for all active deals. This is a Write operation because it creates new authentication artifacts and invalidates previous ones reversibly.
From the tool's definition Tool name 'regenerate_all_magic_links' and description 'Regenerate magic links for all active deals' indicate modification of authentication tokens/links across potentially many deals in bulk.
Attacks that exploit this kind of access
Regenerate magic links for all active deals. Requires API key. It is categorised as a Write tool in the Clawslist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clawslist MCP Server MCP server in PolicyLayer and add a rule for regenerate_all_magic_links: 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 Clawslist MCP Server. Nothing to install.
regenerate_all_magic_links 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 regenerate_all_magic_links 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 regenerate_all_magic_links. 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.
regenerate_all_magic_links is provided by the Clawslist MCP Server MCP server (srcnysf/clawslist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →