Test specific tRPC endpoint with detailed response
AI agents invoke test_trpc_endpoint to trigger actions in N Lobby MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a network request to a specific tRPC endpoint. While 'test' implies diagnostic intent, it actually triggers real endpoint calls whose effects depend on the endpoint being targeted (could be read-only or cause side effects). The description is vague about what endpoints can be targeted or whether writes/mutations are possible, so Execute is the most appropriate category given the ambiguity.
From the tool's definition 'Test specific tRPC endpoint with detailed response' — actively calls/executes a tRPC endpoint
Documented attack patterns abuse exactly the kind of access test_trpc_endpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N Lobby MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test_trpc_endpoint:
{
"version": "1",
"default": "deny",
"tools": {
"test_trpc_endpoint": {
"limits": [
{
"counter": "test_trpc_endpoint_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}test_trpc_endpoint stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test specific tRPC endpoint with detailed response. It is categorised as a Execute tool in the N Lobby MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the N Lobby MCP Server MCP server in PolicyLayer and add a rule for test_trpc_endpoint: 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 N Lobby MCP Server. Nothing to install.
test_trpc_endpoint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_trpc_endpoint 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_trpc_endpoint. 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_trpc_endpoint is provided by the N Lobby MCP Server MCP server (minagishl/nlobby-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N Lobby MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 N Lobby MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.