create_saved_filter
Create a saved table filter.
This record as markdown: /tools/webcake-storefront/create-saved-filter.md
What create_saved_filter does on Webcake Storefront
AI agents use create_saved_filter to create or update resources in Webcake Storefront, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webcake Storefront environment.
Why create_saved_filter is rated Medium
The tool creates a new saved filter, which is a data creation operation (Write category). The severity is low because saved filters are metadata configurations that do not affect core business data, inventory, orders, or financial records. The action is reversible—filters can be modified or deleted. No code execution, deletion, or financial impact is involved.
From the tool's definition Tool name 'create_saved_filter' and description 'Create a saved table filter' indicate creation of a new filter configuration. This is a write operation that creates data persistently but reversibly.
Attacks that exploit this kind of access
The rule that runs create_saved_filter safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_saved_filter, this is the rule to start with:
create_saved_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 Webcake Storefront, apply this rule, and every create_saved_filter call is checked against it from then on.
Questions about create_saved_filter
Create a saved table filter. It is categorised as a Write tool in the Webcake Storefront MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for create_saved_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 Webcake Storefront. Nothing to install.
create_saved_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_saved_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_saved_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_saved_filter is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue