AI agents call proxy_fight to retrieve information from Open Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the context of the server (governance and AGM disclosures for investors) and the pattern of sibling tools which are all data retrieval and parsing operations, 'proxy_fight' most likely retrieves or queries proxy fight information related to shareholder governance.
From the tool's definition Tool name 'proxy_fight' with empty description; sibling tools are all read-only data retrieval tools (agm_agenda_xml, agm_aoi_change_xml, agm_financials_xml, etc.) that fetch and parse governance disclosures for Korean stocks.
Documented attack patterns abuse exactly the kind of access proxy_fight gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Open Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for proxy_fight:
{
"version": "1",
"default": "deny",
"tools": {
"proxy_fight": {}
}
}proxy_fight is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
proxy_fight. It is categorised as a Read tool in the Open Proxy MCP Server, which means it retrieves data without modifying state.
Register the Open Proxy MCP server in PolicyLayer and add a rule for proxy_fight: 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 Open Proxy. Nothing to install.
proxy_fight 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 proxy_fight 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 proxy_fight. 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.
proxy_fight is provided by the Open Proxy MCP server (marcoyou/open-proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Open Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
54 Open Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.