Get all projects from your article queue
AI agents call get_projects to retrieve information from Semantic Pen MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project data without side effects. It is a straightforward query operation that lists existing projects. There is no data modification, code execution, financial transaction, or destructive action involved. The low severity reflects that unauthorized access to project metadata poses minimal risk compared to other categories.
From the tool's definition Tool name is "get_projects" and description states "Get all projects from your article queue" - purely a retrieval operation with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Get all projects from your article queue. It is categorised as a Read tool in the Semantic Pen MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Semantic Pen MCP Server MCP server in PolicyLayer and add a rule for get_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 Semantic Pen MCP Server. Nothing to install.
get_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 get_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 get_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.
get_projects is provided by the Semantic Pen MCP Server MCP server (pushkarsingh32/semantic-pen-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 →