stateset_saved_search
Save and manage search queries
This record as markdown: /tools/stateset-mcp-server/stateset-saved-search.md
What stateset_saved_search does on Stateset
AI agents use stateset_saved_search to create or update resources in Stateset, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stateset environment.
Why stateset_saved_search is rated Medium
The tool saves and manages search queries, which involves writing data (persisting search configurations) to the system. 'Manage' could also imply updating or deleting saved searches, but the primary action is creating/storing, making Write the most appropriate category. Severity is medium since misuse could create unwanted saved searches or modify existing ones, but the blast radius is limited.
From the tool's definition 'Save and manage search queries' indicates creating/storing search configurations
Attacks that exploit this kind of access
The rule that runs stateset_saved_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_saved_search, this is the rule to start with:
stateset_saved_search 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 Stateset, apply this rule, and every stateset_saved_search call is checked against it from then on.
Questions about stateset_saved_search
Save and manage search queries. It is categorised as a Write tool in the Stateset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_saved_search: 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 Stateset. Nothing to install.
stateset_saved_search 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 stateset_saved_search 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 stateset_saved_search. 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.
stateset_saved_search is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
This server
Across the catalogue