Low Risk

filter_us_location

Decide whether a location string looks non-US. Returns { likelyNonUS: boolean }. Use before deciding to keep or discard a job posting when usOnly mode is active.

Part of the Jobsync MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call filter_us_location to retrieve information from Jobsync 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 filter_us_location 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.

jobsync.yaml
tools:
  filter_us_location:
    rules:
      - action: allow

See the full Jobsync policy for all 21 tools.

Tool Name filter_us_location
Category Read
MCP Server Jobsync MCP Server
Risk Level Low

View all 21 tools →

Agents calling read-class tools like filter_us_location have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the filter_us_location tool do? +

Decide whether a location string looks non-US. Returns { likelyNonUS: boolean }. Use before deciding to keep or discard a job posting when usOnly mode is active.. It is categorised as a Read tool in the Jobsync MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on filter_us_location? +

Add a rule in your Intercept YAML policy under the tools section for filter_us_location. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Jobsync MCP server.

What risk level is filter_us_location? +

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

Can I rate-limit filter_us_location? +

Yes. Add a rate_limit block to the filter_us_location rule in your Intercept 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 filter_us_location completely? +

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

filter_us_location is provided by the Jobsync MCP server (jobsync-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.