get_context_info

THE RISK

Low Risk

Why get_context_info needs a policy

This tool retrieves or queries contextual information about the FiftyOne environment state. No side effects, modifications, or destructive operations are implied. The action is informational only, making it a Read operation with minimal risk if misused by an AI agent.

From the tool's definition Tool name 'get_context_info' and description 'Gets information about the current FiftyOne' indicate retrieval of context metadata without modification.

Documented attack patterns abuse exactly the kind of access get_context_info gives an agent:

POLICY

How to control get_context_info

PolicyLayer is an MCP gateway — it sits between your AI agents and FiftyOne MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_context_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_context_info": {}
  }
}

get_context_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register FiftyOne MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More FiftyOne MCP Server tools

Execute execute_operator Execute any FiftyOne operator. Provides Execute execute_pipeline Execute a multi-stage operator pipeline. Execute launch_app Launches the FiftyOne App server. Required Execute download_plugin Downloads and installs a FiftyOne plugin Write clear_view Clears the current view from the session, Write reset_color_scheme Reset the App color scheme to the dataset or Write untag_samples Remove tags from samples in a dataset. Write add_sample_field Add a new field with an explicit type to a

All 47 FiftyOne MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_context_info

What does the get_context_info tool do? +

Gets information about the current FiftyOne. It is categorised as a Read tool in the FiftyOne MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_context_info? +

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

What risk level is get_context_info? +

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

Can I rate-limit get_context_info? +

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

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

get_context_info is provided by the FiftyOne MCP Server MCP server (voxel51/fiftyone-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 FiftyOne MCP Server tool call.

Start from FiftyOne MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →