Low Risk

get_ip_info

get_ip_info

How to control get_ip_info ↓

What get_ip_info does on JoeSandboxMCP

AI agents call get_ip_info to retrieve information from JoeSandboxMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_ip_info needs a policy

This tool retrieves IP-related information from Joe Sandbox analysis results. No description is provided, but the naming convention and context strongly indicate a read-only data retrieval operation with no side effects. Confidence is not higher due to the empty description, but the 'get_' prefix is a strong signal.

From the tool's definition Tool name 'get_ip_info' follows the 'get_' prefix pattern consistent with sibling tools (get_ai_summaries, get_analysis_info, get_domain_info, get_dropped_files, get_dropped_info, get_memory_dumps, get_pcap_file, get_process_info, get_signature_info).

Documented attack patterns abuse exactly the kind of access get_ip_info gives an agent:

How to control get_ip_info

PolicyLayer is an MCP gateway — it sits between your AI agents and JoeSandboxMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_ip_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_ip_info": {}
  }
}

get_ip_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register JoeSandboxMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_ip_info

What does the get_ip_info tool do? +

get_ip_info. It is categorised as a Read tool in the JoeSandboxMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ip_info? +

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

What risk level is get_ip_info? +

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

Can I rate-limit get_ip_info? +

Yes. Add a rate_limit block to the get_ip_info 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 get_ip_info completely? +

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

get_ip_info is provided by the JoeSandbox MCP server (joesecurity/joesandboxmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every JoeSandboxMCP tool call.

Start from JoeSandboxMCP, 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.

15 JoeSandboxMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.