Low Risk

get_motor

Fetch a single Mercury motor by id or slug, including pricing, shaft length, and deep-link URL.

Part of the Harris Boat Works - Mercury Repower server.

get_motor 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 HARRIS BOAT WORKS - MERCURY REPOWER →

Free to start. No card required.

AI agents call get_motor to retrieve information from Harris Boat Works - Mercury Repower 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_motor 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_motor": {}
  }
}

See the full Harris Boat Works - Mercury Repower policy for all 5 tools.

Get this rule live on your own Harris Boat Works - Mercury Repower server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HARRIS BOAT WORKS - MERCURY REPOWER →

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

SECURE HARRIS BOAT WORKS - MERCURY REPOWER →

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

What does the get_motor tool do? +

Fetch a single Mercury motor by id or slug, including pricing, shaft length, and deep-link URL.. It is categorised as a Read tool in the Harris Boat Works - Mercury Repower MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_motor? +

Register the Harris Boat Works - Mercury Repower MCP server in PolicyLayer and add a rule for get_motor: 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 Harris Boat Works - Mercury Repower. Nothing to install.

What risk level is get_motor? +

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

Can I rate-limit get_motor? +

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

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

get_motor is provided by the Harris Boat Works - Mercury Repower MCP server (https://eutsoqdpjurknjsshxes.supabase.co/functions/v1/agent-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Harris Boat Works - Mercury Repower tool call.

Deterministic rules across all 5 Harris Boat Works - Mercury Repower 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.