AI agents call div_detail 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.
Based on naming convention and context as a Korean stock governance disclosure platform, 'div_detail' most likely retrieves dividend information without modifying data. The absence of description and lack of write/execute keywords in the tool name prevents higher confidence, but the server's read-only disclosure purpose and sibling tools all being data retrieval operations (XML parsing, agenda fetching) strongly…
From the tool's definition Tool name 'div_detail' suggests retrieval of dividend details; sibling tools are all read-only data fetching operations (agm_agenda_xml, agm_financials_xml, etc.) consistent with a disclosure/reporting data server. Description is empty, reducing confidence.
Documented attack patterns abuse exactly the kind of access div_detail 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 div_detail:
{
"version": "1",
"default": "deny",
"tools": {
"div_detail": {}
}
}div_detail 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.
div_detail. 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 div_detail: 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.
div_detail 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 div_detail 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 div_detail. 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.
div_detail 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.