Search for jobs in a Phrase TMS project using structured filters. Prefer this over tms_list_jobs when filtering by multiple fields at once (e.g. status + target language + filename). Returns matching jobs with full metadata. (POST /api2/v1/projects/{projectUid}/jobs/search)
AI agents call tms_search_jobs to retrieve information from Phrase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries job data from a Phrase TMS project using filters. It has no side effects—it does not create, modify, delete, or execute external operations. The POST method is used for query filtering, which is standard for complex search operations. The blast radius of misuse is limited to information disclosure of job metadata within the project.
From the tool's definition Tool name 'tms_search_jobs' and description 'Search for jobs' indicates data retrieval. The description explicitly states it 'Returns matching jobs with full metadata' and uses POST only for structured filtering, with no mention of modification, deletion, or…
Attacks that exploit this kind of access
Search for jobs in a Phrase TMS project using structured filters. Prefer this over tms_list_jobs when filtering by multiple fields at once (e.g. status + target language + filename). Returns matching jobs with full metadata. (POST /api2/v1/projects/{projectUid}/jobs/search). It is categorised as a Read tool in the Phrase MCP Server, which means it retrieves data without modifying state.
Register the Phrase MCP server in PolicyLayer and add a rule for tms_search_jobs: 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 Phrase. Nothing to install.
tms_search_jobs 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 tms_search_jobs 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 tms_search_jobs. 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.
tms_search_jobs is provided by the Phrase MCP server (phrase-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 →