securitypass_finding_detail
Fetch a single finding including PoC payload (curl / prompt / payload) and remediation. PoC is generated, never auto-fired.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/securitypass-finding-detail.md
What securitypass_finding_detail does on UnClick
AI agents call securitypass_finding_detail 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 |
|---|---|---|---|
finding_id | string | Yes |
Parameters from the server's own tool schema.
Why securitypass_finding_detail is rated Low
This tool retrieves information about security findings and proof-of-concept payloads but does not execute, modify, or delete anything. The explicit note that PoCs are 'never auto-fired' confirms this is purely informational/Read behavior. While the PoC content itself may be sensitive, the tool's function is querying/fetching, which places it in the Read category.
From the tool's definition Tool description states 'Fetch a single finding' which retrieves data about security findings, and explicitly clarifies that 'PoC is generated, never auto-fired' — indicating no code execution or side effects. The action is data retrieval only.
Attacks that exploit this kind of access
The rule that runs securitypass_finding_detail 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 securitypass_finding_detail, this is the rule to start with:
securitypass_finding_detail 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 securitypass_finding_detail call is checked against it from then on.
Questions about securitypass_finding_detail
Fetch a single finding including PoC payload (curl / prompt / payload) and remediation. PoC is generated, never auto-fired. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
securitypass_finding_detail accepts 1 parameter: finding_id. Required: finding_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 securitypass_finding_detail: 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.
securitypass_finding_detail 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 securitypass_finding_detail 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 securitypass_finding_detail. 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.
securitypass_finding_detail 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