Low Risk

get_variable_relationships

Retrieve analyzed variable relationships for a completed paper. Only returns results when get_analysis_status reports status='Ready'. Without an API key (anonymous): returns the relationship list with source, target, and direction — but detailed reasoning is available only with an API key. Sign u...

Part of the Hypathesis server.

get_variable_relationships 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 HYPATHESIS →

Free to start. No card required.

AI agents call get_variable_relationships to retrieve information from Hypathesis 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_variable_relationships 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_variable_relationships": {}
  }
}

See the full Hypathesis policy for all 4 tools.

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

ENFORCE ON MY HYPATHESIS →

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

SECURE HYPATHESIS →

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

What does the get_variable_relationships tool do? +

Retrieve analyzed variable relationships for a completed paper. Only returns results when get_analysis_status reports status='Ready'. Without an API key (anonymous): returns the relationship list with source, target, and direction — but detailed reasoning is available only with an API key. Sign up at https://hypathesis.com to get one. Args: file_id: The file_id returned by the /upload endpoint. authorization: Optional. API key as 'Bearer hk_...' or 'hk_...'. Returns: Authenticated: full details (source, target, directed, reason per relationship; name, measure per variable). Anonymous: gated (source, target, directed per relationship; name per variable; sign_up_url for full access).. It is categorised as a Read tool in the Hypathesis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_variable_relationships? +

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

What risk level is get_variable_relationships? +

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

Can I rate-limit get_variable_relationships? +

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

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

get_variable_relationships is provided by the Hypathesis MCP server (https://hypathesis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hypathesis tool call.

Deterministic rules across all 4 Hypathesis 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.