check_secrets

check_secrets

Server Trust Security jaden-jjh/trust-security-scanner
Category Read
Risk class Low
Parameters 00 required

What check_secrets does on Trust Security

AI agents call check_secrets 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.

Why check_secrets needs a policy

The tool is part of a security scanning suite focused on detection (DAST/SAST) of vulnerabilities and exposed secrets. Named 'check_secrets', it likely scans for and reports discovered secrets without modifying or deleting them. This is a Read operation (retrieves security findings).

From the tool's definition Tool name 'check_secrets' and context of 'trust-security' server description mentioning 'identifying exposed secrets' indicates this retrieves or detects secrets in code/repositories.

Questions about check_secrets

What does the check_secrets tool do? +

check_secrets. It is categorised as a Read tool in the Trust Security MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_secrets? +

Register the Trust Security MCP server in PolicyLayer and add a rule for check_secrets: 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.

What risk level is check_secrets? +

check_secrets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_secrets? +

Yes. Add a rate_limit block to the check_secrets 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.

How do I block check_secrets completely? +

Set action: deny in the PolicyLayer policy for check_secrets. 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.

What MCP server provides check_secrets? +

check_secrets 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.