This record as markdown: /tools/ashlesh-t-cognirepo/org-search.md
What org_search does on CogniRepo
AI agents call org_search to retrieve information from CogniRepo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why org_search is rated Low
The tool searches data without modifying it, placing it in the Read category. Severity is medium rather than low because search across organizational/agent context could expose sensitive information or allow enumeration of private data if the agent is compromised. However, no direct side effects or data modification occur.
From the tool's definition Tool name 'org_search' and server context indicate querying/searching organizational or contextual data within a persistent memory system. Related sibling tools include 'cross_repo_search' and 'episodic_search', which are clearly Read operations.
Attacks that exploit this kind of access
The rule that runs org_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CogniRepo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For org_search, this is the rule to start with:
org_search 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 CogniRepo, apply this rule, and every org_search call is checked against it from then on.
Questions about org_search
org_search is a read tool on the CogniRepo MCP server. It is categorised as a Read tool in the CogniRepo MCP Server, which means it retrieves data without modifying state.
Register the CogniRepo MCP server in PolicyLayer and add a rule for org_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 CogniRepo. Nothing to install.
org_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 org_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 org_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.
org_search is provided by the CogniRepo MCP server (pypi:cognirepo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CogniRepo, and thousands of servers like it.
This server
Across the catalogue