Perform semantic search across KURA Notes. Returns relevant notes based on the query with metadata.
AI agents call kura_search to retrieve information from KURA Notes MCP Client without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns data (notes and metadata) in response to a semantic search query. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It is purely a read operation, the lowest risk category.
From the tool's definition Tool name 'kura_search' and description 'Perform semantic search across KURA Notes. Returns relevant notes based on the query with metadata' indicate a query/retrieval operation with no modification of data.
Attacks that exploit this kind of access
Perform semantic search across KURA Notes. Returns relevant notes based on the query with metadata. It is categorised as a Read tool in the KURA Notes MCP Client MCP Server, which means it retrieves data without modifying state.
Register the KURA Notes MCP Client MCP server in PolicyLayer and add a rule for kura_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 KURA Notes MCP Client. Nothing to install.
kura_search 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 kura_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 kura_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.
kura_search is provided by the KURA Notes MCP Client MCP server (tillmatthis/kura-notes-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 →