This record as markdown: /tools/io-github-bitsandtea-postking-mcp/web-search.md
What web_search does on Postking Mcp
AI agents call web_search to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why web_search is rated Low
Web search is a read-only operation that queries external data sources and returns results without modifying, deleting, or executing code. The empty description lowers confidence slightly, but the tool name strongly indicates a retrieval function typical of Read-category tools.
From the tool's definition Tool named 'web_search' with no description provided. Standard interpretation of 'search' operations is data retrieval without side effects.
Attacks that exploit this kind of access
The rule that runs web_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_search, this is the rule to start with:
web_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every web_search call is checked against it from then on.
Questions about web_search
web_search is a read tool on the Postking MCP server. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for web_search: 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 Postking Mcp. Nothing to install.
web_search 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 web_search 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 web_search. 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.
web_search is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
This server
Across the catalogue