generate_functional_objectives · Mipiti MCP Server MCP

WHAT IT DOES

What generate_functional_objectives does on Mipiti MCP Server

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

This tool generates functional objectives within a security posture management platform. While generation could theoretically be read-only output, in the context of a management platform with sibling tools that explicitly add and create artifacts, 'generate' most likely produces and persists objectives as part of the threat modeling workflow. This constitutes Write (reversible creation of data) rather than Read.

From the tool's definition Tool name 'generate_functional_objectives' combined with sibling tools like 'add_functional_test', 'add_evidence', and 'add_model_to_system' that create and modify security posture data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_functional_objectives Rate-limited

generate_functional_objectives 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": {
    "generate_functional_objectives": {
      "limits": [
        {
          "counter": "generate_functional_objectives_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 generate_functional_objectives

What does the generate_functional_objectives tool do? +

generate_functional_objectives. 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 generate_functional_objectives? +

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

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

Can I rate-limit generate_functional_objectives? +

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

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

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