submit_to_psi · Timesheet Assistant MCP: Risk & Policy

WHAT IT DOES

What submit_to_psi does on Timesheet Assistant MCP

AI agents invoke submit_to_psi to trigger actions in Timesheet Assistant MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why submit_to_psi needs a policy

This tool triggers an external operation (submitting a timesheet for approval to an external system via browser automation). It is not merely writing local data — it commits a record to a third-party project server for formal approval, making it an Execute-level action. Misuse could result in incorrect timesheets being officially submitted, causing payroll/HR issues, hence high severity.

From the tool's definition Submit already-filled timesheet to PSI Project Server for final approval... uses browser automation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_to_psi Rate-limited

submit_to_psi stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_to_psi": {
      "limits": [
        {
          "counter": "submit_to_psi_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about submit_to_psi

What does the submit_to_psi tool do? +

Submit already-filled timesheet to PSI Project Server for final approval. The tool will automatically read the existing comment from the filled timesheet. Use this after fill_to_psi when you want to submit separately. It is categorised as a Execute tool in the Timesheet Assistant MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_to_psi? +

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

What risk level is submit_to_psi? +

submit_to_psi is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit submit_to_psi? +

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

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

submit_to_psi is provided by the Timesheet Assistant MCP server (sharadmathuratthepsi/timesheet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.