Low Risk

get_app_intro

Friendly introduction to OpenJob for job seekers. Use when the user is new or asks how this works. Return plain language only.

Part of the OpenJob server.

get_app_intro is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OPENJOB →

Free to start. No card required.

AI agents call get_app_intro to retrieve information from OpenJob without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_app_intro only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_app_intro": {}
  }
}

See the full OpenJob policy for all 5 tools.

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

ENFORCE ON MY OPENJOB →

These attack patterns abuse exactly the kind of access get_app_intro 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 get_app_intro only ever does what you allow.

SECURE OPENJOB →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_app_intro tool do? +

Friendly introduction to OpenJob for job seekers. Use when the user is new or asks how this works. Return plain language only.. It is categorised as a Read tool in the OpenJob MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_app_intro? +

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

What risk level is get_app_intro? +

get_app_intro is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_app_intro? +

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

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

get_app_intro is provided by the OpenJob MCP server (https://openjobs-3168f222.alpic.live). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenJob tool call.

Deterministic rules across all 5 OpenJob 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.