AI agents call get_harness to retrieve information from Loadbay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | the harness slug, e.g. browser-use |
Parameters from the server's own tool schema.
This tool retrieves and queries harness metadata by its identifier (slug). It performs no modification, deletion, execution, or financial transaction. It is a straightforward data retrieval operation with no blast radius beyond exposing catalog information already intended to be public.
From the tool's definition Tool name 'get_harness' and description 'Get full details for one harness by its slug' indicate a retrieval operation with no side effects. The verb 'Get' and the purpose of fetching details confirms read-only behavior.
Attacks that exploit this kind of access
Get full details for one harness by its slug. It is categorised as a Read tool in the Loadbay MCP Server, which means it retrieves data without modifying state.
get_harness accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Loadbay MCP server in PolicyLayer and add a rule for get_harness: 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 Loadbay. Nothing to install.
get_harness is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_harness 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.
Set action: deny in the PolicyLayer policy for get_harness. 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.
get_harness is provided by the Loadbay MCP server (https://loadbay.xyz/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_harness is one line of Loadbay's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →