save_search
Save a search query and get notified when new matching listings appear in your area. The Sourcing Agent monitors new listings and proactively alerts you.
This record as markdown: /tools/nitrostack/save-search.md
What save_search does on Nitrostack
AI agents use save_search to create or update resources in Nitrostack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nitrostack environment.
Why save_search is rated Medium
Tool creates and stores saved search configuration; reversible write operation with moderate scope.
From the tool's definition Save a search query, get notified when new matching listings appear
Attacks that exploit this kind of access
The rule that runs save_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_search, this is the rule to start with:
save_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 Nitrostack, apply this rule, and every save_search call is checked against it from then on.
Questions about save_search
Save a search query and get notified when new matching listings appear in your area. The Sourcing Agent monitors new listings and proactively alerts you. It is categorised as a Write tool in the Nitrostack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nitrostack MCP server in PolicyLayer and add a rule for save_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 Nitrostack. Nothing to install.
save_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 save_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 save_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.
save_search is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
This server
Across the catalogue