get_search_areas
Get available search documents and areas.
This record as markdown: /tools/gentel-lab-origenemcp/get-search-areas.md
What get_search_areas does on OrigeneMCP
AI agents call get_search_areas to retrieve information from OrigeneMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_search_areas is rated Low
This tool retrieves metadata about available search documents and areas—a pure read operation with no side effects, data modification, code execution, or irreversible actions. The blast radius of misuse is minimal as it only exposes the schema or inventory of searchable content.
From the tool's definition Tool name 'get_search_areas' and description 'Get available search documents and areas' indicate a retrieval operation that lists or queries available search options without modifying data.
Attacks that exploit this kind of access
The rule that runs get_search_areas safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OrigeneMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_search_areas, this is the rule to start with:
get_search_areas 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 OrigeneMCP, apply this rule, and every get_search_areas call is checked against it from then on.
Questions about get_search_areas
Get available search documents and areas. It is categorised as a Read tool in the OrigeneMCP MCP Server, which means it retrieves data without modifying state.
Register the Origene MCP server in PolicyLayer and add a rule for get_search_areas: 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 OrigeneMCP. Nothing to install.
get_search_areas 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 get_search_areas 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 get_search_areas. 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.
get_search_areas is provided by the Origene MCP server (gentel-lab/origenemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Origene, and thousands of servers like it.
This server
Across the catalogue