Test all LLM providers to check their availability and functionality.
AI agents call test_llm_providers to retrieve information from Session Buddy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool tests/checks LLM providers for availability and functionality - a read/diagnostic operation that queries provider status. It does not modify data, execute user code, or perform destructive actions. The word 'test' in context means health-checking, similar to a ping or connectivity check. Minor side effect of making outbound requests, but no data modification occurs.
From the tool's definition Test all LLM providers to check their availability and functionality
Attacks that exploit this kind of access
Test all LLM providers to check their availability and functionality. It is categorised as a Read tool in the Session Buddy MCP Server, which means it retrieves data without modifying state.
Register the Session Buddy MCP server in PolicyLayer and add a rule for test_llm_providers: 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 Session Buddy. Nothing to install.
test_llm_providers 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 test_llm_providers 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 test_llm_providers. 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.
test_llm_providers is provided by the Session Buddy MCP server (lesleslie/session-buddy). 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 →