qc_check_api
Test a list of API endpoints and report which ones return the expected HTTP status. Runs each endpoint sequentially.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/qc-check-api.md
What qc_check_api does on UnClick
AI agents invoke qc_check_api to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
base_url | string | Yes | Base URL for all endpoints (e.g. https://api.example.com) |
endpoints | array | Yes | List of endpoints to test |
Parameters from the server's own tool schema.
Why qc_check_api is rated High
This tool executes HTTP requests against a list of API endpoints, which constitutes running external operations. The effects depend on the endpoints provided (they could trigger side effects on remote systems). It is not merely reading local data; it sends network requests that could interact with live services.
From the tool's definition 'Test a list of API endpoints' and 'Runs each endpoint sequentially' — the tool actively makes HTTP requests to external endpoints
Risk signalsAccepts file system path (endpoints[].path) · Accepts URL/endpoint input (base_url)
Attacks that exploit this kind of access
The rule that runs qc_check_api 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 qc_check_api, this is the rule to start with:
qc_check_api stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 qc_check_api call is checked against it from then on.
Questions about qc_check_api
Test a list of API endpoints and report which ones return the expected HTTP status. Runs each endpoint sequentially. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
qc_check_api accepts 2 parameters: base_url, endpoints. Required: base_url, endpoints. 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 qc_check_api: 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.
qc_check_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the qc_check_api 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 qc_check_api. 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.
qc_check_api 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.
Across the catalogue