Starting point for localization integration assessment. Fetches the remote project list with sandbox state, returns the correct client URL patterns for both production and non-production environments, and provides a full classification guide so the agent can determine whether the local project is...
AI agents call assess_integration_state to retrieve information from Localization without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectSlug | string | — | Optional: the project slug to fetch full details for |
Parameters from the server's own tool schema.
This tool performs information retrieval tasks: fetching project lists, returning URL patterns, and providing classification data. It has no capability to create, modify, delete, execute code, or trigger external operations. The description indicates it is an assessment/diagnostic tool designed as a starting point for evaluation, which is characteristic of Read category tools.
From the tool's definition Tool description explicitly states 'Fetches the remote project list', 'returns the correct client URL patterns', and 'provides a full classification guide' — all read-only operations that retrieve and query data without modification or side effects.
Attacks that exploit this kind of access
Starting point for localization integration assessment. Fetches the remote project list with sandbox state, returns the correct client URL patterns for both production and non-production environments, and provides a full classification guide so the agent can determine whether the local project is correctly integrated. Use this as the first tool call when running /assess or whenever you need to evaluate how (or whether) a consumer app is connected to this localization backend. If projectSlug is provided, also fetches full project details (locales, namespaces, sandbox state) for that specific project. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
assess_integration_state accepts 1 parameter: projectSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Localization MCP server in PolicyLayer and add a rule for assess_integration_state: 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 Localization. Nothing to install.
assess_integration_state 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 assess_integration_state 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 assess_integration_state. 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.
assess_integration_state is provided by the Localization MCP server (localization-mcp-server). 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 →