Return basic information about the server host.
AI agents call get_system_info to retrieve information from Friday MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely queries and returns system metadata (hostname, OS, architecture, etc.). It has no side effects, does not execute commands, does not modify data, and does not access sensitive user data beyond basic host properties. The blast radius of misuse is minimal; an attacker learns environmental details but cannot directly compromise the system or access protected data through this tool alone.
From the tool's definition Tool name is 'get_system_info' and description states it returns 'basic information about the server host' — a read-only retrieval operation with no modification or execution of external code.
Attacks that exploit this kind of access
Return basic information about the server host. It is categorised as a Read tool in the Friday MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Friday MCP Server 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 Friday MCP Server. 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 Friday MCP Server MCP server (jeremylakeyjr/mcp-server). 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 →