proxy_refresh

Re-discover tools from all internal MCP sub-services.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/proxy-refresh.md

WHAT IT DOES

What proxy_refresh does on Odoo Claude MCP

AI agents invoke proxy_refresh to trigger actions in Odoo Claude MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why proxy_refresh is rated High

This tool triggers an active re-discovery/refresh operation across internal MCP sub-services. It executes an external operation (scanning/probing sub-services) rather than simply reading existing data or writing a record. Misuse could disrupt service discovery or cause unintended side effects across multiple sub-services, warranting medium severity.

From the tool's definition Re-discover tools from all internal MCP sub-services

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxy_refresh safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxy_refresh, this is the rule to start with:

proxy_refresh Rate-limited

proxy_refresh stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proxy_refresh": {
      "limits": [
        {
          "counter": "proxy_refresh_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every proxy_refresh call is checked against it from then on.

FAQ

Questions about proxy_refresh

What does the proxy_refresh tool do? +

Re-discover tools from all internal MCP sub-services. It is categorised as a Execute tool in the Odoo Claude MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on proxy_refresh? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for proxy_refresh: 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 Odoo Claude MCP. Nothing to install.

What risk level is proxy_refresh? +

proxy_refresh is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit proxy_refresh? +

Yes. Add a rate_limit block to the proxy_refresh 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.

How do I block proxy_refresh completely? +

Set action: deny in the PolicyLayer policy for proxy_refresh. 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 proxy_refresh? +

proxy_refresh is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →