Search weclapp API knowledge across entities, fields, endpoints, and relationships.
AI agents call search_knowledge to retrieve information from Weclapp Api Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about the weclapp API structure, entities, fields, endpoints, and relationships. It performs read-only lookups against a knowledge base with no capability to modify data, execute external operations, or trigger state changes. This is a standard Read category tool with minimal security risk.
From the tool's definition Tool description states it 'Search[es] weclapp API knowledge' which is a retrieval operation. The sibling tools (analyze_response_structure, check_field_presence, compare_approaches, etc.) further confirm this server provides passive exploration and querying…
Attacks that exploit this kind of access
Search weclapp API knowledge across entities, fields, endpoints, and relationships. It is categorised as a Read tool in the Weclapp Api Knowledge MCP Server, which means it retrieves data without modifying state.
Register the Weclapp Api Knowledge MCP server in PolicyLayer and add a rule for search_knowledge: 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 Weclapp Api Knowledge. Nothing to install.
search_knowledge 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_knowledge 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_knowledge. 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_knowledge is provided by the Weclapp Api Knowledge MCP server (serenmind/weclapp-api-knowledgebase-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 →