mark_job · Local Tech Digest MCP: Risk & Policy

WHAT IT DOES

What mark_job does on Local Tech Digest

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

WHY IT NEEDS A POLICY

Why mark_job needs a policy

This tool creates or modifies data reversibly: updating an application status is a write operation that can be undone (status can be changed again). It does not delete data, execute code, move money, or trigger external systems. The severity is medium because misuse could clutter job tracking state, but the blast radius is limited to a single user's local digest and application records.

From the tool's definition Tool description states 'Update the application status of a job by its ID' — modifies data (application status) for a specific job record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_job Rate-limited

mark_job 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": {
    "mark_job": {
      "limits": [
        {
          "counter": "mark_job_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 Local Tech Digest, so you can run agents against it safely.

FAQ

Questions about mark_job

What does the mark_job tool do? +

Update the application status of a job by its ID. It is categorised as a Write tool in the Local Tech Digest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_job? +

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

What risk level is mark_job? +

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

Can I rate-limit mark_job? +

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

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

mark_job is provided by the Local Tech Digest MCP server (nk1947-sudo/local-tech-digest-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.