list_layouts
List available layout engines and output formats
This record as markdown: /tools/jrmatherly-mcp-context-forge/list-layouts.md
What list_layouts does on ContextForge MCP Gateway
AI agents call list_layouts to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_layouts is rated Low
The tool retrieves and displays configuration or metadata about available layout engines and formats. This is a pure read operation with no capability to modify, delete, or execute code. It poses minimal risk to system integrity or data confidentiality, making it low severity. High confidence is warranted because the description is clear and unambiguous.
From the tool's definition Tool description explicitly states 'List available layout engines and output formats' — a query/enumeration operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_layouts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_layouts, this is the rule to start with:
list_layouts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every list_layouts call is checked against it from then on.
Questions about list_layouts
List available layout engines 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_layouts: 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_layouts 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_layouts 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_layouts. 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_layouts 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.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue