Check security advisories and dependencies for a package version.
AI agents call check_security to retrieve information from Github Insight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves security advisory information and dependency data from sources like deps.dev without modifying any data or executing code. It purely queries and reports information, fitting the Read category. The severity is low since a misuse would only result in gathering or analyzing security information, with minimal blast radius.
From the tool's definition check_security performs security advisory and dependency checking, which are informational queries with no modifications or side effects.
Attacks that exploit this kind of access
Check security advisories and dependencies for a package version. It is categorised as a Read tool in the Github Insight MCP Server, which means it retrieves data without modifying state.
Register the Github Insight MCP server in PolicyLayer and add a rule for check_security: 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 Github Insight. Nothing to install.
check_security 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 check_security 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 check_security. 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.
check_security is provided by the Github Insight MCP server (wjddusrb03/github-insight-mcp). 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 →