securitypass_disclosure_status
Check the 90+30 responsible-disclosure timer state for a finding (notified, acked, extended, public, withdrawn).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/securitypass-disclosure-status.md
What securitypass_disclosure_status does on UnClick
AI agents call securitypass_disclosure_status 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_disclosure_status is rated Low
This is a read-only operation that queries the current status of a security disclosure timeline (notified, acked, extended, public, or withdrawn). It retrieves information about a finding's responsible-disclosure status without modifying, executing, or deleting anything. The blast radius of misuse is minimal—an agent could only learn unwanted information about disclosure states, not cause harm or change any data.
From the tool's definition The tool 'Check the 90+30 responsible-disclosure timer state for a finding' performs a lookup operation that retrieves the status of a disclosure timer.
Attacks that exploit this kind of access
The rule that runs securitypass_disclosure_status 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_disclosure_status, this is the rule to start with:
securitypass_disclosure_status 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_disclosure_status call is checked against it from then on.
Questions about securitypass_disclosure_status
Check the 90+30 responsible-disclosure timer state for a finding (notified, acked, extended, public, withdrawn). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
securitypass_disclosure_status 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_disclosure_status: 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_disclosure_status 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_disclosure_status 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_disclosure_status. 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_disclosure_status 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