search_by_tags
AI agents call search_by_tags to retrieve information from RSpace MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_by_tags' clearly indicates retrieval/querying of data without modification. In the context of a research data management system (RSpace), tag-based search would retrieve documents or samples matching specified tags. This is a read operation with no side effects.
From the tool's definition Tool name 'search_by_tags' indicates a search operation, which is a read-only query. The sibling tools on this server (create_*, add_*, bulk_create_*) are all write/destructive operations, positioning this as a read capability.
Attacks that exploit this kind of access
search_by_tags. It is categorised as a Read tool in the RSpace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RSpace MCP Server MCP server in PolicyLayer and add a rule for search_by_tags: 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 RSpace MCP Server. Nothing to install.
search_by_tags 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_tags 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_tags. 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_tags is provided by the RSpace MCP Server MCP server (rspace-os/rspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →