collect_legacy_project_intake · MCP SAPUI5 Server MCP

WHAT IT DOES

What collect_legacy_project_intake does on MCP SAPUI5 Server

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

WHY IT NEEDS A POLICY

Why collect_legacy_project_intake needs a policy

This tool creates or stores project metadata and contextual information (legacy project intake data). This is a Write operation because it modifies system state by persisting new data. It's not Read-only since it actively stores information; it's not Execute since it doesn't run arbitrary code or trigger external operations; it's not Destructive since the action is reversible; it's not Financial.

From the tool's definition The tool 'collect_legacy_project_intake' performs actions to 'collect and persist' data, where 'persist' indicates storage/modification of state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

collect_legacy_project_intake Rate-limited

collect_legacy_project_intake 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": {
    "collect_legacy_project_intake": {
      "limits": [
        {
          "counter": "collect_legacy_project_intake_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 MCP SAPUI5 Server, so you can run agents against it safely.

FAQ

Questions about collect_legacy_project_intake

What does the collect_legacy_project_intake tool do? +

Collect and persist legacy-project contextual intake to improve AI guidance quality while minimizing repeated prompts/tokens. It is categorised as a Write tool in the MCP SAPUI5 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 collect_legacy_project_intake? +

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

What risk level is collect_legacy_project_intake? +

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

Can I rate-limit collect_legacy_project_intake? +

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

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

collect_legacy_project_intake is provided by the MCP SAPUI5 Server MCP server (santiagosanmartinn/mcpui5server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.