Search Knowledge Base articles by keywords (relevance-ranked).
AI agents call search_kb_articles to retrieve information from InvGate Service Desk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves data from a knowledge base without side effects. It matches the 'Read' category definition: retrieves or queries data with no side effects (search, list, get, fetch). The search operation is non-destructive and cannot modify system state, incidents, or any other data. Severity is low as misuse poses no significant risk to the service or organization.
From the tool's definition Tool description states it 'Search[es] Knowledge Base articles by keywords' — a retrieval operation with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
Search Knowledge Base articles by keywords (relevance-ranked). It is categorised as a Read tool in the InvGate Service Desk MCP Server, which means it retrieves data without modifying state.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for search_kb_articles: 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.
search_kb_articles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_kb_articles 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 search_kb_articles. 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.
search_kb_articles 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 →