Browse all available TestRail API categories and their methods.
AI agents call browse_testrail_api to retrieve information from TestRail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only introspection of the TestRail API schema. It returns informational metadata to help users understand what operations are available, analogous to a help or documentation lookup. There is no capability to execute commands, modify data, or trigger external operations.
From the tool's definition The tool 'browse_testrail_api' is described as browsing/listing 'all available TestRail API categories and their methods.' This is a discovery and query operation with no side effects—it retrieves metadata about available API endpoints without modifying,…
Attacks that exploit this kind of access
Browse all available TestRail API categories and their methods. It is categorised as a Read tool in the TestRail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for browse_testrail_api: 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 TestRail MCP Server. Nothing to install.
browse_testrail_api 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 browse_testrail_api 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 browse_testrail_api. 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.
browse_testrail_api is provided by the TestRail MCP Server MCP server (trtmn/tram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →