Get all findings data from OnSecurity from client in a high level summary, only include the summary, not the raw data and be sure to present the data in a way that is easy to understand for the client. You can optionally filter findings by round_id. HOWEVER ONLY USE THIS TOOL WHEN ASKED FOR FINDI...
AI agents call get-findings to retrieve information from OnSecurity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves security findings data from the OnSecurity system. It performs a read operation with filtering capabilities but does not create, modify, delete, execute commands, or commit financial transactions. The optional filtering parameter does not change the fundamental read-only nature of the operation.
From the tool's definition Tool retrieves 'all findings data' in 'high level summary' form with optional filtering by round_id. The description explicitly states it 'Get[s]' data and instructs 'only include the summary, not the raw data', indicating read-only retrieval with no…
Attacks that exploit this kind of access
Get all findings data from OnSecurity from client in a high level summary, only include the summary, not the raw data and be sure to present the data in a way that is easy to understand for the client. You can optionally filter findings by round_id. HOWEVER ONLY USE THIS TOOL WHEN ASKED FOR FINDINGS RELATED TO A CLIENT OR MY FINDINGS, NOT THE BLOCKS TOOL. It is categorised as a Read tool in the OnSecurity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OnSecurity MCP Server MCP server in PolicyLayer and add a rule for get-findings: 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 OnSecurity MCP Server. Nothing to install.
get-findings 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 get-findings 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 get-findings. 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.
get-findings is provided by the OnSecurity MCP Server MCP server (onsecurity/onsecurity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →