Create a Knowledge Base article.
AI agents use create_kb_article to create or update resources in InvGate Service Desk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your InvGate Service Desk environment.
This tool creates new data (a knowledge base article) which is reversible—articles can be edited, archived, or deleted later. It does not execute code, move money, or permanently destroy data. The blast radius is minimal: worst case, an AI creates unhelpful or incorrect articles that must be manually reviewed and removed. This fits the Write category.
From the tool's definition Tool name 'create_kb_article' and description 'Create a Knowledge Base article' indicate creation of new content in a knowledge base system.
Attacks that exploit this kind of access
Create a Knowledge Base article. It is categorised as a Write tool in the InvGate Service Desk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for create_kb_article: 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 InvGate Service Desk. Nothing to install.
create_kb_article 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 create_kb_article 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 create_kb_article. 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.
create_kb_article is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). 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 →