Update an existing concept\
AI agents use update_concept to create or update resources in Concept Tracker — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Concept Tracker environment.
This tool modifies data reversibly—it updates concept definitions/metadata in the searchable knowledge base without deleting information or executing arbitrary code. It falls clearly into the Write category. Severity is medium because misuse could corrupt the knowledge base structure or inject false technical information, but damage is reversible via re-extraction or manual correction.
From the tool's definition Tool description states 'Update an existing concept' which modifies existing data in the knowledge base. Sibling tools show this is a knowledge base management system where concepts can be added, deleted, exported, extracted, retrieved, and listed.
Attacks that exploit this kind of access
Update an existing concept\. It is categorised as a Write tool in the Concept Tracker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Concept Tracker MCP server in PolicyLayer and add a rule for update_concept: 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 Concept Tracker. Nothing to install.
update_concept 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_concept 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_concept. 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_concept is provided by the Concept Tracker MCP server (liwengggou/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 →