AI agents call get_finding_schema 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 the schema/structure of findings data with no side effects. It is a read-only query operation typical of schema inspection in reporting systems. While the description is empty, the naming pattern and context strongly suggest data retrieval without modification or destructive capability.
From the tool's definition Tool name is 'get_finding_schema' and it belongs to a pentest reporting system. The 'get_' prefix indicates data retrieval. No description provided, but sibling tools like 'list_findings' and 'get_finding_details' are clearly Read operations.
Documented attack patterns abuse exactly the kind of access get_finding_schema 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_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_finding_schema": {}
}
}get_finding_schema 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.
get_finding_schema. 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_schema: 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_schema 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_schema 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_schema. 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_schema 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.