security_digest

Generate security summary across all managed repos

Server Git Steer ry-ops/git-steer
Category Read
Risk class Low
Parameters 00 required

What security_digest does on Git Steer

AI agents call security_digest to retrieve information from Git Steer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why security_digest needs a policy

The tool queries and aggregates security information across repositories to produce a summary report. This is a read-only operation that retrieves and presents data without creating, modifying, deleting, executing, or moving resources. No destructive, financial, or code-execution capabilities are implied.

From the tool's definition Tool name and description indicate 'Generate security summary' — a retrieval and reporting function with no modification or execution.

Questions about security_digest

What does the security_digest tool do? +

Generate security summary across all managed repos. It is categorised as a Read tool in the Git Steer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on security_digest? +

Register the Git Steer MCP server in PolicyLayer and add a rule for security_digest: 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 Git Steer. Nothing to install.

What risk level is security_digest? +

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

Can I rate-limit security_digest? +

Yes. Add a rate_limit block to the security_digest 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 security_digest completely? +

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

security_digest is provided by the Git Steer MCP server (ry-ops/git-steer). 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.