get_findings
Retrieve security findings filtered by file or severity. Run scan_repository first to populate results.
This record as markdown: /tools/com-graneth-mcp-server/get-findings.md
What get_findings does on Mcp Server
AI agents call get_findings to retrieve information from Mcp Server 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 |
|---|---|---|---|
file | string | — | Filter findings to a specific file path |
repo | string | Yes | GitHub repository name |
owner | string | Yes | GitHub repository owner |
severity | string | — | Filter by severity level |
Parameters from the server's own tool schema.
Why get_findings is rated Low
This tool retrieves and filters existing security findings without modifying, deleting, or executing anything. It is purely informational, similar to a search or get operation. The filtering parameters (file, severity) are applied to already-scanned data, not to trigger new operations or mutations.
From the tool's definition Tool name 'get_findings' and description 'Retrieve security findings' indicates a query/retrieval operation with no side effects. The instruction to 'Run scan_repository first to populate results' confirms this is a read-only accessor of pre-computed data.
Risk signalsAccepts file system path (file)
Attacks that exploit this kind of access
The rule that runs get_findings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_findings, this is the rule to start with:
get_findings 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 Mcp Server, apply this rule, and every get_findings call is checked against it from then on.
Questions about get_findings
Retrieve security findings filtered by file or severity. Run scan_repository first to populate results. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_findings accepts 4 parameters: file, repo, owner, severity. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the 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 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 Mcp Server MCP server (@graneth/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue