update_saved_search
Update a saved search
This record as markdown: /tools/danielsimonjr-memory-mcp/update-saved-search.md
What update_saved_search does on Enhanced Knowledge Graph Memory Server
AI agents use update_saved_search to create or update resources in Enhanced Knowledge Graph Memory Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Knowledge Graph Memory Server environment.
Why update_saved_search is rated Medium
This tool modifies stored search configurations, which is a reversible write operation. It does not delete data (would be Destructive), execute external code (would be Execute), or move financial resources (would be Financial). The 'update' operation on a search object in a knowledge graph storage system is characteristic of Write category.
From the tool's definition Tool name 'update_saved_search' indicates modification of existing saved search data. The server description emphasizes 'persistent knowledge graph storage' and the sibling tools like 'add_tags', 'add_observations', 'add_procedure' confirm this is a data…
Attacks that exploit this kind of access
The rule that runs update_saved_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_saved_search, this is the rule to start with:
update_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 Enhanced Knowledge Graph Memory Server, apply this rule, and every update_saved_search call is checked against it from then on.
Questions about update_saved_search
Update a saved search. It is categorised as a Write tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for update_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 Enhanced Knowledge Graph Memory Server. Nothing to install.
update_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 update_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 update_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.
update_saved_search is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue