Medium Risk

my-resume

获取我的简历,输出简历原始内容

Part of the Liepin Jobs server.

my-resume can modify Liepin Jobs data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LIEPIN JOBS →

Free to start. No card required.

AI agents use my-resume to create or modify resources in Liepin Jobs. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call my-resume repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Liepin Jobs.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "my-resume": {
      "limits": [
        {
          "counter": "my-resume_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Liepin Jobs policy for all 14 tools.

Get this rule live on your own Liepin Jobs server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LIEPIN JOBS →

View all 14 tools →

These attack patterns abuse exactly the kind of access my-resume gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so my-resume only ever does what you allow.

SECURE LIEPIN JOBS →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the my-resume tool do? +

获取我的简历,输出简历原始内容. It is categorised as a Write tool in the Liepin Jobs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on my-resume? +

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

What risk level is my-resume? +

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

Can I rate-limit my-resume? +

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

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

my-resume is provided by the Liepin Jobs MCP server (https://open-agent.liepin.com/mcp/user). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Liepin Jobs tool call.

Deterministic rules across all 14 Liepin Jobs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.