Analyse a company
AI agents call get_github_velocity to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes publicly available GitHub data about a company's development activity. It performs no modifications, deletions, or financial transactions. The blast radius of misuse is minimal—an AI agent could retrieve unwanted intelligence about a competitor or target, but cannot execute code, delete data, or commit financial resources.
From the tool's definition Tool name 'get_github_velocity' and description 'Analyse a company' indicate data retrieval and analysis. The tool queries GitHub metrics to analyze developer activity/velocity for a company—a read-only intelligence operation.
Attacks that exploit this kind of access
Analyse a company. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_github_velocity: 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 Omni Service Node. Nothing to install.
get_github_velocity 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_github_velocity 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_github_velocity. 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_github_velocity is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →