Retrieve project metadata such as name, terms count, and last activity. Useful before performing other operations on the project.
AI agents call project_details to retrieve information from POEditor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays metadata about a translation project. It performs no mutations, side effects, or external actions. This is a pure data retrieval operation, fitting the 'Read' category for querying data with no side effects.
From the tool's definition Tool description states 'Retrieve project metadata such as name, terms count, and last activity' — this is a read-only operation that queries project information without modification.
Attacks that exploit this kind of access
Retrieve project metadata such as name, terms count, and last activity. Useful before performing other operations on the project. It is categorised as a Read tool in the POEditor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the POEditor MCP Server MCP server in PolicyLayer and add a rule for project_details: 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 POEditor MCP Server. Nothing to install.
project_details 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 project_details 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 project_details. 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.
project_details is provided by the POEditor MCP Server MCP server (ryan-shaw/poeditor-mcp). 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 →