IMPORTANT: Call this BEFORE writing code for a project. Returns full conventions, patterns, record types, templates, packages, and rules that the generated code MUST follow.
AI agents call get_project_context to retrieve information from Prowpt 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 and queries project configuration metadata to inform code generation. It performs a read operation with no modifications, deletions, or external execution. The severity is low because the data returned is project metadata and configuration, not sensitive credentials or user data, and access is constrained to the AI agent's current project context.
From the tool's definition Tool name 'get_project_context' and description 'Returns full conventions, patterns, record types, templates, packages, and rules' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
IMPORTANT: Call this BEFORE writing code for a project. Returns full conventions, patterns, record types, templates, packages, and rules that the generated code MUST follow. It is categorised as a Read tool in the Prowpt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for get_project_context: 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 Prowpt MCP Server. Nothing to install.
get_project_context 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_project_context 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_project_context. 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_project_context is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-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 →