Get system and directory information for debugging
AI agents call get_system_info to retrieve information from Recipe Research MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about the system and directories. While it performs a read operation (no modification of data), the severity is elevated to 'medium' because exposing system and directory information could enable reconnaissance attacks or information disclosure vulnerabilities that aid in further exploitation.
From the tool's definition Tool name 'get_system_info' and description 'Get system and directory information for debugging' indicate retrieval of system metadata and filesystem structure without modification.
Attacks that exploit this kind of access
Get system and directory information for debugging. It is categorised as a Read tool in the Recipe Research MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Recipe Research 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 Recipe Research 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 Recipe Research MCP Server MCP server (suraj-yadav-aiml/recipe-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 →