Manually add a new technical concept to the knowledge base.
AI agents use add_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 creates or modifies data (adds a new concept to the knowledge base) in a reversible manner. The operation is not destructive (no deletion), does not execute arbitrary code or external operations, and has no financial implications. The blast radius is low because adding a concept to a documentation/knowledge base has minimal downstream impact—it can be easily corrected via update_concept or delete_concept.
From the tool's definition Tool name 'add_concept' and description 'Manually add a new technical concept to the knowledge base' indicate creation of new data entries in a searchable knowledge base.
Attacks that exploit this kind of access
Manually add a new technical concept to the knowledge base. 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 add_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.
add_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 add_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 add_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.
add_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 →