AI agents call get_knowledge_base to retrieve information from WeKnora MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a knowledge base without creating, modifying, or deleting data. It is a simple query operation that returns details, consistent with the Read category pattern. The low severity reflects minimal blast radius—an AI agent misusing this would only over-query or access knowledge base metadata, not cause irreversible harm.
From the tool's definition Tool name 'get_knowledge_base' and description 'Get knowledge base details' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_knowledge_base gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WeKnora MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_knowledge_base:
{
"version": "1",
"default": "deny",
"tools": {
"get_knowledge_base": {}
}
}get_knowledge_base is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get knowledge base details. It is categorised as a Read tool in the WeKnora MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WeKnora MCP Server MCP server in PolicyLayer and add a rule for get_knowledge_base: 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 WeKnora MCP Server. Nothing to install.
get_knowledge_base 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 get_knowledge_base 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 get_knowledge_base. 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.
get_knowledge_base is provided by the WeKnora MCP Server MCP server (nannaolympicbroadcast/weknoramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WeKnora MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 WeKnora MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.