get_client_info

SERVER3TG Test Generation SOURCEhttps://mcp.3tg.dev/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-3tg-mcp/get-client-info.md

WHAT IT DOES

What get_client_info does on 3TG Test Generation

AI agents call get_client_info to retrieve information from 3TG Test Generation without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`clientId`	string	Yes	The 3tg.dev clientId to inspect.

Parameters from the server's own tool schema.

RISK

Why get_client_info is rated Low

This tool performs a read-only query of account metadata. It returns information about a 3tg.dev clientId without modifying any data, consuming resources, or triggering downstream operations. The explicit mention that it does not consume credits reinforces that it is a passive lookup operation.

From the tool's definition Tool description explicitly states 'Look up account info' and 'WITHOUT consuming any credits.' It retrieves account information (plan name, quotas, dates, flags) with no side effects, modifications, or external operations triggered.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_client_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 3TG Test Generation, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_client_info, this is the rule to start with:

get_client_info Allowed

get_client_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 3TG Test Generation, apply this rule, and every get_client_info call is checked against it from then on.

FAQ

Questions about get_client_info

What does the get_client_info tool do? +

Look up account info for a 3tg.dev clientId WITHOUT consuming any credits. Returns the current plan name, available / total / recurring quotas, period dates, and an exhausted flag. Credit-consumption model (so you can explain the numbers to the user accurately): - 1 credit = 1 generated test case (a single test(...) / it(...) block in the emitted .test.ts / .test.tsx). - Credits are consumed ONLY by test generation — i.e. by the create_tests and create_tests_from_spec tools. Spec generation (create_spec, create_spec_for_function), mock generation (create_mock_for_function), this lookup tool, and create_agent_instructions / help are all FREE. - The available field below is the number of test cases the client can still produce in the current period. Use this for: - Verifying a freshly-entered clientId during /mcp__3tg__configure before saving it to .3tg/credentials.json. - Reporting current quota / plan to the user. - Pre-flight checks so the agent can warn early if quota is low. Errors: - INVALID_CLIENT_ID — license-api rejected the clientId (typo, suspended, wrong product). - LICENSE_API_UNAVAILABLE — transient network / DNS / TLS failure. Note: quota exhaustion is NOT an error here — the response carries exhausted: true and the QuotaInfo for the agent to surface. It is categorised as a Read tool in the 3TG Test Generation MCP Server, which means it retrieves data without modifying state.

What parameters does get_client_info accept? +

get_client_info accepts 1 parameter: clientId. Required: clientId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_client_info? +

Register the 3TG Test Generation MCP server in PolicyLayer and add a rule for get_client_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 3TG Test Generation. Nothing to install.

What risk level is get_client_info? +

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

Can I rate-limit get_client_info? +

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

Set action: deny in the PolicyLayer policy for get_client_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_client_info? +

get_client_info is provided by the 3TG Test Generation MCP server (https://mcp.3tg.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 3TG Test Generation, and thousands of servers like it.

This server

All 10 3TG Test Generation tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →