Low Risk

get_submission

Get submission details by UUID.

How to control get_submission ↓

What get_submission does on Threat Zone MCP Server

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

Low Risk

Why get_submission needs a policy

This tool retrieves existing submission metadata by identifier. It has no side effects, cannot modify or delete data, and does not execute code or perform financial operations. The low severity reflects minimal blast radius—even if misused by an agent, querying submission details causes no damage. Confidence is high given the clear read-only semantics.

From the tool's definition Tool name 'get_submission' and description 'Get submission details by UUID' indicate a retrieval operation.

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

How to control get_submission

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

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

get_submission 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 Threat Zone MCP Server — 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_submission

What does the get_submission tool do? +

Get submission details by UUID. It is categorised as a Read tool in the Threat Zone MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_submission? +

Register the Threat Zone MCP Server MCP server in PolicyLayer and add a rule for get_submission: 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 Threat Zone MCP Server. Nothing to install.

What risk level is get_submission? +

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

Can I rate-limit get_submission? +

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

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

get_submission is provided by the Threat Zone MCP Server MCP server (threat-zone/threatzonemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Threat Zone MCP Server tool call.

Start from Threat Zone MCP Server, 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.

31 Threat Zone MCP Server 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.