Get project-wide type information for better type inference
AI agents call get_project_context to retrieve information from MCP Pyrefly Autotype Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing type information from a project to support type inference. It has no side effects, does not execute code, does not modify files, and does not delete anything. It is a straightforward data retrieval operation, making it a Read category tool with low severity.
From the tool's definition The tool name is 'get_project_context' and the description states it retrieves 'project-wide type information'. The verb 'get' and the read-only nature of retrieving context information for inference purposes indicate no modification or execution of code.
Attacks that exploit this kind of access
Get project-wide type information for better type inference. It is categorised as a Read tool in the MCP Pyrefly Autotype Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Pyrefly Autotype 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 MCP Pyrefly Autotype 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 MCP Pyrefly Autotype Server MCP server (lolpack/mcp-pyrefly-autotype). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_project_context is one line of MCP Pyrefly Autotype Server'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 →