create_npr_filter
Apply a non-photorealistic painterly filter to an existing TOP. A generalized Kuwahara (sector-based local variance smoothing) runs in a single GLSL TOP and branches into three looks selected by
This record as markdown: /tools/hybridlabor-api-aos/create-npr-filter.md
What create_npr_filter does on Aos
AI agents use create_npr_filter to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why create_npr_filter is rated Medium
This tool modifies data (visual/image content) by applying a filter effect, which is a reversible transformation. It does not delete, destroy, or execute arbitrary code—it renders a specific visual effect. This fits the Write category: creates or modifies data reversibly.
From the tool's definition "Apply a non-photorealistic painterly filter to an existing TOP" and "runs in a single GLSL TOP" indicate the tool modifies visual data in TouchDesigner (applies a filter/shader transformation to a TOP node), creating a new visual state.
Attacks that exploit this kind of access
The rule that runs create_npr_filter safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_npr_filter, this is the rule to start with:
create_npr_filter 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 Aos, apply this rule, and every create_npr_filter call is checked against it from then on.
Questions about create_npr_filter
Apply a non-photorealistic painterly filter to an existing TOP. A generalized Kuwahara (sector-based local variance smoothing) runs in a single GLSL TOP and branches into three looks selected by. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for create_npr_filter: 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 Aos. Nothing to install.
create_npr_filter 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 create_npr_filter 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 create_npr_filter. 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.
create_npr_filter is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue