submit_findings · Mipiti MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_findings does on Mipiti MCP Server

AI agents use submit_findings 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_findings needs a policy

This tool creates/posts new findings data records to a security platform, which is reversible (findings can be updated or deleted later). It modifies platform state but does not irreversibly delete data, execute arbitrary code, move money, or trigger external operations. The 'submit' verb and context of posting security findings to a threat model system places it in Write category.

From the tool's definition Tool name 'submit_findings' and description 'Submit negative findings discovered by scanning codebase' indicate it creates or posts findings records to the Mipiti security posture platform, modifying the threat model and compliance state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_findings Rate-limited

submit_findings 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_findings": {
      "limits": [
        {
          "counter": "submit_findings_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_findings

What does the submit_findings tool do? +

Submit negative findings discovered by scanning codebase. 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_findings? +

Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for submit_findings: 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_findings? +

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

Can I rate-limit submit_findings? +

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

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

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