AI agents call search_by_tag to retrieve information from Memlord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name clearly indicates a search/query operation, which retrieves data without modification or deletion. The empty description lowers confidence slightly, but the naming pattern and sibling tools strongly suggest this is a Read category tool. A memory server's search function would logically return matching results without altering state.
From the tool's definition Tool name 'search_by_tag' indicates a query operation to find memories by tag. Given sibling tools like 'get_memory', 'list_memories', 'recall_memory', and 'retrieve_memory', this tool appears to be a read-only search function.
Documented attack patterns abuse exactly the kind of access search_by_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memlord, and nothing reaches the server without passing your rules. This is the rule we recommend for search_by_tag:
{
"version": "1",
"default": "deny",
"tools": {
"search_by_tag": {}
}
}search_by_tag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_by_tag. It is categorised as a Read tool in the Memlord MCP Server, which means it retrieves data without modifying state.
Register the Memlord MCP server in PolicyLayer and add a rule for search_by_tag: 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 Memlord. Nothing to install.
search_by_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_by_tag 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 search_by_tag. 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.
search_by_tag is provided by the Memlord MCP server (myrikld/memlord). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memlord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Memlord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.