AI agents call cursor_func to retrieve information from Ida Domain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple information retrieval operation typical of debugging/analysis workflows. It queries the current state of IDA Pro to return function metadata, with no side effects, data modification, or external operations. The low severity reflects minimal blast radius—misuse would only return information already accessible within the IDA environment.
From the tool's definition Tool name 'cursor_func' and description 'Get current function' indicate a read-only query operation that retrieves information about the currently selected function in IDA Pro without modifying any state.
Documented attack patterns abuse exactly the kind of access cursor_func gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ida Domain, and nothing reaches the server without passing your rules. This is the rule we recommend for cursor_func:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_func": {}
}
}cursor_func 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.
Get current function. It is categorised as a Read tool in the Ida Domain MCP Server, which means it retrieves data without modifying state.
Register the Ida Domain MCP server in PolicyLayer and add a rule for cursor_func: 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 Ida Domain. Nothing to install.
cursor_func 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 cursor_func 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 cursor_func. 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.
cursor_func is provided by the Ida Domain MCP server (xxyyue/ida_domain_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ida Domain, 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.
74 Ida Domain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.