Get results of a GitHub repo scan by scan ID.
AI agents call get_repo_scan_result to retrieve information from Trust Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only fetches and returns previously-generated scan results. It has no side effects, does not modify data, execute code, or trigger new scans. It is a straightforward data retrieval operation with minimal security risk in isolation, though the results themselves may contain sensitive vulnerability information that could inform an attacker.
From the tool's definition Tool name is 'get_repo_scan_result' and description states 'Get results of a GitHub repo scan by scan ID' — this retrieves/queries existing scan data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get results of a GitHub repo scan by scan ID. It is categorised as a Read tool in the Trust Security MCP Server, which means it retrieves data without modifying state.
Register the Trust Security MCP server in PolicyLayer and add a rule for get_repo_scan_result: 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 Trust Security. Nothing to install.
get_repo_scan_result 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_repo_scan_result 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_repo_scan_result. 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_repo_scan_result is provided by the Trust Security MCP server (jaden-jjh/trust-security-scanner). 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 →