Gets the full details of a specific finding by its ID.
AI agents call get_finding_details to retrieve information from Reptor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from the SysReptor pentest reporting system without modifying, deleting, or executing any operations. It is a straightforward read operation that returns information about a specific finding based on its ID, consistent with tools like 'list_findings' in the same category. No destructive, financial, or code execution capabilities are present.
From the tool's definition Tool name 'get_finding_details' and description 'Gets the full details of a specific finding by its ID' clearly indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_finding_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reptor, and nothing reaches the server without passing your rules. This is the rule we recommend for get_finding_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_finding_details": {}
}
}get_finding_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets the full details of a specific finding by its ID. It is categorised as a Read tool in the Reptor MCP Server, which means it retrieves data without modifying state.
Register the Reptor MCP server in PolicyLayer and add a rule for get_finding_details: 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 Reptor. Nothing to install.
get_finding_details 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_finding_details 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_finding_details. 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_finding_details is provided by the Reptor MCP server (slvnlrt/reptor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reptor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Reptor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.