AI agents use update_tags to create or update resources in Skill Cortex Lite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Skill Cortex Lite environment.
Update operations that modify metadata (tags) are reversible Write operations. Without a description, confidence is reduced, but the name and context strongly suggest tag modification. Severity is medium because misuse could corrupt skill organization and discoverability but wouldn't delete skills or execute arbitrary code. Not higher severity since tags are typically non-critical metadata.
From the tool's definition Tool name is 'update_tags' which indicates modification of metadata. Context shows this server manages 'skills' with related operations including create, delete, get, list, and search.
Documented attack patterns abuse exactly the kind of access update_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Skill Cortex Lite, and nothing reaches the server without passing your rules. This is the rule we recommend for update_tags:
{
"version": "1",
"default": "deny",
"tools": {
"update_tags": {
"limits": [
{
"counter": "update_tags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_tags stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update_tags. It is categorised as a Write tool in the Skill Cortex Lite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Skill Cortex Lite MCP server in PolicyLayer and add a rule for update_tags: 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 Skill Cortex Lite. Nothing to install.
update_tags 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_tags 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_tags. 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_tags is provided by the Skill Cortex Lite MCP server (sim-xia/skill-cortex-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Skill Cortex Lite, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Skill Cortex Lite tools catalogued and risk-classified — across an index of 43,000+ MCP servers.