Update Nuclei templates to latest version.
AI agents use update_templates to create or update resources in Security Scanner MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Security Scanner MCP Server environment.
This tool modifies template files used by the Nuclei scanner. While updates are generally benign maintenance operations, they alter system state and could potentially introduce unwanted template changes or break scanning workflows if a bad version is deployed.
From the tool's definition Tool name 'update_templates' and description 'Update Nuclei templates to latest version' indicate modification of existing data (templates). The action is reversible—templates can be reverted to previous versions or re-downloaded.
Attacks that exploit this kind of access
Update Nuclei templates to latest version. It is categorised as a Write tool in the Security Scanner MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Security Scanner MCP Server MCP server in PolicyLayer and add a rule for update_templates: 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 Security Scanner MCP Server. Nothing to install.
update_templates 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 update_templates 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 update_templates. 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.
update_templates is provided by the Security Scanner MCP Server MCP server (marc-shade/security-scanner-mcp). 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 →