Get NetworkLytics API information and available endpoints.
AI agents call get_api_info to retrieve information from Networklytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches informational content about API structure and endpoints—a read-only operation with no capability to execute commands, modify data, delete resources, or trigger external actions. The blast radius is minimal as it only exposes API documentation. Confidence is high because the description unambiguously describes a retrieval operation.
From the tool's definition Tool name 'get_api_info' and description 'Get NetworkLytics API information and available endpoints' indicate retrieval of metadata about the service with no modifications, side effects, or code execution.
Attacks that exploit this kind of access
Get NetworkLytics API information and available endpoints. It is categorised as a Read tool in the Networklytics MCP Server, which means it retrieves data without modifying state.
Register the Networklytics MCP server in PolicyLayer and add a rule for get_api_info: 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 Networklytics. Nothing to install.
get_api_info 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_api_info 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_api_info. 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_api_info is provided by the Networklytics MCP server (leekangbum/networklytics-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 →