Show a specific component, category, or collection in the staging browser. Returns navigation metadata. Set show_first=true to auto-select the first component in the collection.
Single-target operation
Part of the Tesseract MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call studio_show_component to retrieve information from Tesseract 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 studio_show_component 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.
tools:
studio_show_component:
rules:
- action: allowSee the full Tesseract policy for all 46 tools.
Agents calling read-class tools like studio_show_component have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Show a specific component, category, or collection in the staging browser. Returns navigation metadata. Set show_first=true to auto-select the first component in the collection.. It is categorised as a Read tool in the Tesseract MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for studio_show_component. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Tesseract MCP server.
studio_show_component 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 studio_show_component 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.
Set action: deny in the Intercept policy for studio_show_component. 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.
studio_show_component is provided by the Tesseract MCP server (tesseract-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept