submit_functional_tests · Mipiti MCP Server MCP

WHAT IT DOES

What submit_functional_tests does on Mipiti MCP Server

AI agents use submit_functional_tests to create or update resources in Mipiti MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mipiti MCP Server environment.

WHY IT NEEDS A POLICY

Why submit_functional_tests needs a policy

This tool creates or modifies functional test records within a security posture management system. The verb 'submit' indicates an irreversible submission action that persists data, placing it in the Write category.

From the tool's definition Tool name 'submit_functional_tests' combined with sibling tools all prefixed with 'add_' (e.g., add_functional_test, add_evidence) indicates this performs data creation/modification operations on the Mipiti security platform.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_functional_tests Rate-limited

submit_functional_tests stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_functional_tests": {
      "limits": [
        {
          "counter": "submit_functional_tests_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mipiti MCP Server, so you can run agents against it safely.

FAQ

Questions about submit_functional_tests

What does the submit_functional_tests tool do? +

submit_functional_tests. It is categorised as a Write tool in the Mipiti MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_functional_tests? +

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

What risk level is submit_functional_tests? +

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

Can I rate-limit submit_functional_tests? +

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

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

submit_functional_tests is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.