search_by_tag
Find (namespace, key) pairs with a given tag. Returns up to 1000 results.
This record as markdown: /tools/dev-aic0rt3x-memory-mcp/search-by-tag.md
What search_by_tag does on AI Cortex Storage
AI agents call search_by_tag to retrieve information from AI Cortex Storage without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | Yes | Tag to search for. Returns up to 1000 (namespace, key) pairs. |
Parameters from the server's own tool schema.
Why search_by_tag is rated Low
This tool retrieves and searches data without modifying, deleting, or executing anything. It performs a read-only lookup operation against stored memories, returning matching results. The blast radius of misuse is minimal—an agent could query for sensitive namespaces or keys, but cannot alter or delete data. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name 'search_by_tag' and description 'Find (namespace, key) pairs with a given tag. Returns up to 1000 results.' indicate a query/search operation with no side effects.
Attacks that exploit this kind of access
The rule that runs search_by_tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI Cortex Storage, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_by_tag, this is the rule to start with:
search_by_tag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AI Cortex Storage, apply this rule, and every search_by_tag call is checked against it from then on.
Questions about search_by_tag
Find (namespace, key) pairs with a given tag. Returns up to 1000 results. It is categorised as a Read tool in the AI Cortex Storage MCP Server, which means it retrieves data without modifying state.
search_by_tag accepts 1 parameter: tag. Required: tag. The full parameter table on this page comes from the server's own tool schema.
Register the AI Cortex Storage 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 AI Cortex Storage. 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 AI Cortex Storage MCP server (https://memory.aic0rt3x.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI Cortex Storage, and thousands of servers like it.
This server
Across the catalogue