Check Encoding MCP system information. Shows available libraries and supported encodings.
AI agents call get_system_info to retrieve information from Encoding MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval about the system's encoding capabilities and libraries. It has no side effects, does not create or modify data, does not execute code with variable effects, and does not delete or move resources. The read-only nature and minimal scope (system metadata) justify low severity.
From the tool's definition Tool name 'get_system_info' and description 'Shows available libraries and supported encodings' indicate a read-only query operation that retrieves system metadata without modifying state.
Attacks that exploit this kind of access
Check Encoding MCP system information. Shows available libraries and supported encodings. It is categorised as a Read tool in the Encoding MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Encoding 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 Encoding 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 Encoding MCP Server MCP server (whyjp/encoding_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 →