Low Risk

browse_oag_tree

Browse the OAG code hierarchy (object type classification)

Part of the Simap MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call browse_oag_tree to retrieve information from Simap without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though browse_oag_tree only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-digilac-simap-mcp.yaml
tools:
  browse_oag_tree:
    rules:
      - action: allow

See the full Simap policy for all 14 tools.

Tool Name browse_oag_tree
Category Read
MCP Server Simap MCP Server
Risk Level Low

View all 14 tools →

Agents calling read-class tools like browse_oag_tree have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the browse_oag_tree tool do? +

Browse the OAG code hierarchy (object type classification). It is categorised as a Read tool in the Simap MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browse_oag_tree? +

Add a rule in your Intercept YAML policy under the tools section for browse_oag_tree. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Simap MCP server.

What risk level is browse_oag_tree? +

browse_oag_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browse_oag_tree? +

Yes. Add a rate_limit block to the browse_oag_tree rule in your Intercept 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.

How do I block browse_oag_tree completely? +

Set action: deny in the Intercept policy for browse_oag_tree. 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.

What MCP server provides browse_oag_tree? +

browse_oag_tree is provided by the Simap MCP server (@digilac/simap-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Simap

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.