Get IRIS system information for connectivity testing.
AI agents call get_system_info to retrieve information from Iris Execute without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries system information (a read operation) with no side effects. It is used for connectivity testing and status checking, which are passive inspection activities. The blast radius of misuse is minimal—an attacker could learn system details but cannot execute code, modify data, or cause destructive actions. Classification as Read is appropriate.
From the tool's definition Tool name 'get_system_info' and description 'Get IRIS system information for connectivity testing' indicate retrieval of system metadata without modification or execution of arbitrary code.
Attacks that exploit this kind of access
Get IRIS system information for connectivity testing. It is categorised as a Read tool in the Iris Execute MCP Server, which means it retrieves data without modifying state.
Register the Iris Execute MCP server in PolicyLayer and add a rule for get_system_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 Iris Execute. Nothing to install.
get_system_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_system_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_system_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_system_info is provided by the Iris Execute MCP server (jbrandtmse/iris-execute-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 →