Low Risk

get_list_of_recent_analyses

get_list_of_recent_analyses

How to control get_list_of_recent_analyses ↓

What get_list_of_recent_analyses does on JoeSandboxMCP

AI agents call get_list_of_recent_analyses 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_list_of_recent_analyses needs a policy

This tool retrieves or lists historical analysis data from Joe Sandbox Cloud. The naming convention and context of sibling tools indicate a query/retrieval operation with no side effects. No data creation, modification, or deletion capabilities are evident. Severity is low because listing past analyses poses minimal security risk to the system itself.

From the tool's definition Tool name 'get_list_of_recent_analyses' uses the 'get' verb and 'list' pattern, consistent with read-only operations.

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

How to control get_list_of_recent_analyses

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_list_of_recent_analyses:

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

get_list_of_recent_analyses 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_list_of_recent_analyses

What does the get_list_of_recent_analyses tool do? +

get_list_of_recent_analyses. 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_list_of_recent_analyses? +

Register the JoeSandbox MCP server in PolicyLayer and add a rule for get_list_of_recent_analyses: 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_list_of_recent_analyses? +

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

Can I rate-limit get_list_of_recent_analyses? +

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

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

get_list_of_recent_analyses 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.