Low Risk

renderer_settings

Get renderer configuration: toneMapping, exposure, colorSpace, shadowMap, pixelRatio

Part of the Threejs Devtools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call renderer_settings to retrieve information from Threejs Devtools without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though renderer_settings only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

three-js-devtools-mcp.yaml
tools:
  renderer_settings:
    rules:
      - action: allow

See the full Threejs Devtools policy for all 60 tools.

Tool Name renderer_settings
Category Read
Risk Level Low

View all 60 tools →

Agents calling read-class tools like renderer_settings have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the renderer_settings tool do? +

Get renderer configuration: toneMapping, exposure, colorSpace, shadowMap, pixelRatio. It is categorised as a Read tool in the Threejs Devtools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on renderer_settings? +

Add a rule in your Intercept YAML policy under the tools section for renderer_settings. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Threejs Devtools MCP server.

What risk level is renderer_settings? +

renderer_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit renderer_settings? +

Yes. Add a rate_limit block to the renderer_settings rule in your Intercept 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.

How do I block renderer_settings completely? +

Set action: deny in the Intercept policy for renderer_settings. 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.

What MCP server provides renderer_settings? +

renderer_settings is provided by the Threejs Devtools MCP server (threejs-devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Threejs Devtools

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.