List all Texterify projects accessible to the authenticated user. Use this to discover project IDs and names, or to verify the currently configured project. Note: all other tools already operate on the pre-configured project (set via TEXTERIFY_PROJECT_ID environment variable), so this tool is mai...
AI agents call list_projects to retrieve information from Texterify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation that retrieves and returns project information accessible to the authenticated user without modifying, creating, or deleting any data. It is a straightforward discovery/enumeration function with minimal blast radius—the worst outcome of misuse would be exposing project names and IDs to which the user already has access.
From the tool's definition Tool description states it 'List all Texterify projects' and is 'mainly useful for discovery and verification.' It retrieves project metadata with 'no side effects' as indicated by the read-only nature of listing operations.
Attacks that exploit this kind of access
List all Texterify projects accessible to the authenticated user. Use this to discover project IDs and names, or to verify the currently configured project. Note: all other tools already operate on the pre-configured project (set via TEXTERIFY_PROJECT_ID environment variable), so this tool is mainly useful for discovery and verification. The response includes:. It is categorised as a Read tool in the Texterify MCP Server, which means it retrieves data without modifying state.
Register the Texterify MCP server in PolicyLayer and add a rule for list_projects: 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 Texterify. Nothing to install.
list_projects 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 list_projects 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 list_projects. 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.
list_projects is provided by the Texterify MCP server (mogharsallah/texterify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_projects is one line of Texterify's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →