profile.update_candidate · Lore Context MCP: Risk & Policy

WHAT IT DOES

What profile.update_candidate does on Lore Context

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

WHY IT NEEDS A POLICY

Why profile.update_candidate needs a policy

This tool creates or modifies profile data (the candidate update submission). The operation appears reversible—updates can typically be replaced or reverted—placing it in the Write category rather than Destructive.

From the tool's definition Tool name 'update_candidate' and description 'Submit a beta profile update candidate' indicates modification of profile data. The verb 'update' and 'submit' suggest reversible creation or modification of data records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

profile.update_candidate Rate-limited

profile.update_candidate 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": {
    "profile.update_candidate": {
      "limits": [
        {
          "counter": "profile.update_candidate_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 Lore Context, so you can run agents against it safely.

FAQ

Questions about profile.update_candidate

What does the profile.update_candidate tool do? +

Submit a beta profile update candidate when the profile API is available. It is categorised as a Write tool in the Lore Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on profile.update_candidate? +

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

What risk level is profile.update_candidate? +

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

Can I rate-limit profile.update_candidate? +

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

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

profile.update_candidate is provided by the Lore Context MCP server (Lore-Context/lore-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.