List supported input and output formats
AI agents call list_supported_formats to retrieve information from ContextForge MCP Gateway 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 metadata about supported formats—a read-only operation with no side effects, no code execution, and no data modification. It is informational in nature and poses minimal risk even if an AI agent calls it unexpectedly. The low severity reflects the benign nature of format enumeration.
From the tool's definition Tool name 'list_supported_formats' and description 'List supported input and output formats' indicate a retrieval operation that queries available formats without modifying state or triggering external operations.
Attacks that exploit this kind of access
List supported input and output formats. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for list_supported_formats: 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 ContextForge MCP Gateway. Nothing to install.
list_supported_formats 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 list_supported_formats 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 list_supported_formats. 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.
list_supported_formats is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →