Medium Risk

create_test_inbox

Standalone inbox helper for testing. Create or reuse the saved primary disposable email inbox, then use auth_test_assist first when the task is website auth so you also get reusable cross-site strategy and remembered per-site guidance. Returns email, password, inbox ID, and known-site history for...

Part of the Screenshotsmcp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use create_test_inbox to create or modify resources in Screenshotsmcp. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_test_inbox repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Screenshotsmcp.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

relievedattention992-smithery-screenshotsmcp.yaml
tools:
  create_test_inbox:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Screenshotsmcp policy for all 56 tools.

Tool Name create_test_inbox
Category Write
Risk Level Medium

View all 56 tools →

Agents calling write-class tools like create_test_inbox have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the create_test_inbox tool do? +

Standalone inbox helper for testing. Create or reuse the saved primary disposable email inbox, then use auth_test_assist first when the task is website auth so you also get reusable cross-site strategy and remembered per-site guidance. Returns email, password, inbox ID, and known-site history for the reusable inbox.. It is categorised as a Write tool in the Screenshotsmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_test_inbox? +

Add a rule in your Intercept YAML policy under the tools section for create_test_inbox. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Screenshotsmcp MCP server.

What risk level is create_test_inbox? +

create_test_inbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_test_inbox? +

Yes. Add a rate_limit block to the create_test_inbox rule in your Intercept 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 create_test_inbox completely? +

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

create_test_inbox is provided by the Screenshotsmcp MCP server (relievedattention992-smithery/screenshotsmcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Screenshotsmcp

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.