leave.submit_prepared_request

WHAT IT DOES

What leave.submit_prepared_request does on Tlc Portal

AI agents use leave.submit_prepared_request to create or update resources in Tlc Portal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tlc Portal environment.

WHY IT NEEDS A POLICY

Why leave.submit_prepared_request needs a policy

This tool creates a new leave request record in the portal system. It is a Write operation (creating/submitting data) rather than Execute, as it submits a prepared form rather than running arbitrary code. The blast radius is medium — a misuse could submit an unauthorized vacation request on behalf of a user, but it is reversible via the sibling 'leave.cancel_request' tool.

From the tool's definition Submits a previously prepared leave request

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

leave.submit_prepared_request Rate-limited

leave.submit_prepared_request 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": {
    "leave.submit_prepared_request": {
      "limits": [
        {
          "counter": "leave.submit_prepared_request_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 Tlc Portal, so you can run agents against it safely.

FAQ

Questions about leave.submit_prepared_request

What does the leave.submit_prepared_request tool do? +

Submits a previously prepared leave request. It is categorised as a Write tool in the Tlc Portal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on leave.submit_prepared_request? +

Register the Tlc Portal MCP server in PolicyLayer and add a rule for leave.submit_prepared_request: 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 Tlc Portal. Nothing to install.

What risk level is leave.submit_prepared_request? +

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

Can I rate-limit leave.submit_prepared_request? +

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

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

leave.submit_prepared_request is provided by the Tlc Portal MCP server (mingovvv/tlc-portal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.