create_job_details · MCP User Profile Management Server MCP

WHAT IT DOES

What create_job_details does on MCP User Profile Management Server

AI agents use create_job_details to create or update resources in MCP User Profile Management Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP User Profile Management Server environment.

WHY IT NEEDS A POLICY

Why create_job_details needs a policy

This tool creates new data (job postings) reversibly—job postings can be edited or deleted later. It does not execute code, delete data irreversibly, or handle financial transactions. The severity is medium rather than low because job postings may have downstream effects (e.g., recruiting workflows, notifications) depending on system integration, and an AI agent could create spam or misleading postings if misused.

From the tool's definition Tool name 'create_job_details' and description 'Create a new job posting' indicate data creation. The phrase 'with elicitation support for missing fields' confirms the tool accepts and processes user input to populate a new record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_job_details Rate-limited

create_job_details 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": {
    "create_job_details": {
      "limits": [
        {
          "counter": "create_job_details_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 MCP User Profile Management Server, so you can run agents against it safely.

FAQ

Questions about create_job_details

What does the create_job_details tool do? +

Create a new job posting with elicitation support for missing fields. It is categorised as a Write tool in the MCP User Profile Management Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_job_details? +

Register the MCP User Profile Management Server MCP server in PolicyLayer and add a rule for create_job_details: 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 MCP User Profile Management Server. Nothing to install.

What risk level is create_job_details? +

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

Can I rate-limit create_job_details? +

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

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

create_job_details is provided by the MCP User Profile Management Server MCP server (sldragon/mcp-elicitation-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.