stackexchange_search
Search Stack Exchange (default: Stack Overflow) for questions.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/stackexchange-search.md
What stackexchange_search does on UnClick
AI agents call stackexchange_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number. |
site | string | — | SE site (default: stackoverflow). |
query | string | Yes | Search query. |
Parameters from the server's own tool schema.
Why stackexchange_search is rated Low
This tool retrieves and queries public data from Stack Exchange without creating, modifying, deleting, executing code, or incurring financial obligations. The search operation is read-only with no reversible or irreversible changes to any system or data store.
From the tool's definition Tool name 'stackexchange_search' and description 'Search Stack Exchange (default: Stack Overflow) for questions' indicate a search/query operation with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs stackexchange_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stackexchange_search, this is the rule to start with:
stackexchange_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 UnClick, apply this rule, and every stackexchange_search call is checked against it from then on.
Questions about stackexchange_search
Search Stack Exchange (default: Stack Overflow) for questions. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
stackexchange_search accepts 3 parameters: page, site, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for stackexchange_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 UnClick. Nothing to install.
stackexchange_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 stackexchange_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 stackexchange_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.
stackexchange_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue