This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/stackexchange-question.md
What stackexchange_question does on UnClick
AI agents call stackexchange_question 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 |
|---|---|---|---|
id | string | Yes | Question ID. |
site | string | — | SE site (default: stackoverflow). |
Parameters from the server's own tool schema.
Why stackexchange_question is rated Low
This tool retrieves existing data from Stack Exchange without modifying, executing, deleting, or committing any financial transaction. It is a simple query/fetch operation with no side effects, fitting the Read category. The severity is low because Stack Exchange questions are public information with no sensitive data exposure risk or blast radius for an AI agent misuse.
From the tool's definition Tool name and description indicate retrieval only: 'Get a Stack Exchange question by ID' — a straightforward read operation querying public data by identifier.
Attacks that exploit this kind of access
The rule that runs stackexchange_question 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_question, this is the rule to start with:
stackexchange_question 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_question call is checked against it from then on.
Questions about stackexchange_question
Get a Stack Exchange question by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
stackexchange_question accepts 2 parameters: id, site. Required: id. 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_question: 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_question 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_question 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_question. 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_question 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