Get information about this MCP server.
AI agents call server_info to retrieve information from Incident Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about the MCP server itself. It is a simple query operation with no ability to modify state, execute commands, or affect external systems. The blast radius of misuse is minimal—an agent could only learn about server configuration or capabilities, which poses negligible security risk.
From the tool's definition Tool name 'server_info' and description 'Get information about this MCP server' indicate a retrieval operation that queries server metadata without modification or side effects.
Attacks that exploit this kind of access
Get information about this MCP server. It is categorised as a Read tool in the Incident Agent MCP Server, which means it retrieves data without modifying state.
Register the Incident Agent MCP server in PolicyLayer and add a rule for server_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 Incident Agent. Nothing to install.
server_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 server_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 server_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.
server_info is provided by the Incident Agent MCP server (jayliumlp/incident-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
server_info is one line of Incident Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →