update_job_summary · Lapras MCP: Risk & Policy

WHAT IT DOES

What update_job_summary does on Lapras

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

PARAMETERS

Parameter	Type	Required	Description
`job_summary`	string	Yes	Job summary（職務要約）

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_job_summary needs a policy

This tool modifies user profile data (job summary) on the LAPRAS platform in a reversible way. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not involve financial transactions (would be Financial). The impact is medium severity because a compromised AI agent could alter a user's professional profile, but the change can be reverted.

From the tool's definition Tool name is 'update_job_summary' and description states 'Update job summary... on LAPRAS'. The verb 'update' indicates modification of existing data in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_job_summary Rate-limited

update_job_summary 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": {
    "update_job_summary": {
      "limits": [
        {
          "counter": "update_job_summary_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 Lapras, so you can run agents against it safely.

FAQ

Questions about update_job_summary

What does the update_job_summary tool do? +

Update job summary（職務要約） on LAPRAS(https://lapras.com). You can check the result at https://lapras.com/cv. It is categorised as a Write tool in the Lapras MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_job_summary accept? +

update_job_summary accepts 1 parameter: job_summary. Required: job_summary. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_job_summary? +

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

What risk level is update_job_summary? +

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

Can I rate-limit update_job_summary? +

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

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

update_job_summary is provided by the Lapras MCP server (@lapras-inc/lapras-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.