get_project
Fetch a project row — settings, voice config, default style, export URL.
This record as markdown: /tools/com-framesail-framesail/get-project.md
What get_project does on Framesail
AI agents call get_project to retrieve information from Framesail without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
Parameters from the server's own tool schema.
Why get_project is rated Low
This is a straightforward data retrieval operation. It queries existing project information without creating, modifying, deleting, executing code, or moving money. The verb 'Fetch' and the read-only nature of returning configuration and metadata confirm Read category. Severity is low because retrieving project metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'get_project' and description states it 'Fetch[es] a project row' — retrieve-only operation with no modification or side effects. Returns metadata: settings, voice config, default style, and export URL.
Attacks that exploit this kind of access
The rule that runs get_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_project, this is the rule to start with:
get_project is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every get_project call is checked against it from then on.
Questions about get_project
Fetch a project row — settings, voice config, default style, export URL. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
get_project accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for get_project: 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 Framesail. Nothing to install.
get_project 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 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. 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 is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue