set_anti_aliasing
Configure anti-aliasing settings (MSAA, FXAA, TAA)
This record as markdown: /tools/keeveeg-godot-mcp/set-anti-aliasing.md
What set_anti_aliasing does on Godot
AI agents use set_anti_aliasing to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
taa | boolean | — | Enable/disable TAA |
fxaa | boolean | — | Enable/disable FXAA |
msaa | string | — | MSAA level (or omit to disable) |
Parameters from the server's own tool schema.
Why set_anti_aliasing is rated Medium
This tool modifies Godot engine rendering settings in a reversible manner. It configures anti-aliasing parameters, which are graphics preferences that can be changed back or overridden. This is a Write operation because it alters configuration state without executing arbitrary code or causing irreversible destruction.
From the tool's definition Tool name 'set_anti_aliasing' and description 'Configure anti-aliasing settings (MSAA, FXAA, TAA)' indicates modification of rendering configuration settings.
Attacks that exploit this kind of access
The rule that runs set_anti_aliasing safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_anti_aliasing, this is the rule to start with:
set_anti_aliasing stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every set_anti_aliasing call is checked against it from then on.
Questions about set_anti_aliasing
Configure anti-aliasing settings (MSAA, FXAA, TAA). It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_anti_aliasing accepts 3 parameters: taa, fxaa, msaa. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for set_anti_aliasing: 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 Godot. Nothing to install.
set_anti_aliasing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_anti_aliasing 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 set_anti_aliasing. 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.
set_anti_aliasing is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue