update_knowledge_base_article
AI agents use update_knowledge_base_article to create or update resources in RunWhen Platform MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RunWhen Platform MCP environment.
This tool creates or modifies data (knowledge base articles) in a reversible manner, which fits the Write category. Severity is medium because unauthorized updates to knowledge base articles could spread misinformation or degrade documentation quality, but the effect is reversible and doesn't pose financial or destructive risks.
From the tool's definition Tool name 'update_knowledge_base_article' indicates modification of existing knowledge base content. The 'update' verb clearly shows a write/modify operation that is reversible.
Attacks that exploit this kind of access
update_knowledge_base_article. It is categorised as a Write tool in the RunWhen Platform MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for update_knowledge_base_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 RunWhen Platform MCP. Nothing to install.
update_knowledge_base_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 update_knowledge_base_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 update_knowledge_base_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.
update_knowledge_base_article is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-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 →