getProject
Read a single project by id. Auth via the standard project-access ladder. Returns the full v_projects row (id, workspace_id, name, description, icon, created_by/at, updated_by/at). Read-only.
This record as markdown: /tools/io-stablebaseline-sb/getproject.md
What getProject does on Stable Baseline
AI agents call getProject to retrieve information from Stable Baseline 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 UUID. |
Parameters from the server's own tool schema.
Why getProject is rated Low
This tool retrieves project information with no side effects. It queries data using standard authentication (project-access ladder) and returns metadata. The explicit 'Read-only' designation confirms it performs no write, execute, or destructive operations. Severity is low because project metadata is typically non-sensitive business information accessible to authorized users.
From the tool's definition Tool name 'getProject' and description explicitly states 'Read a single project by id' and 'Read-only'. Returns project metadata (id, workspace_id, name, description, icon, timestamps). No modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs getProject safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getProject, this is the rule to start with:
getProject 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 Stable Baseline, apply this rule, and every getProject call is checked against it from then on.
Questions about getProject
Read a single project by id. Auth via the standard project-access ladder. Returns the full v_projects row (id, workspace_id, name, description, icon, created_by/at, updated_by/at). Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getProject 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 Stable Baseline MCP server in PolicyLayer and add a rule for getProject: 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 Stable Baseline. Nothing to install.
getProject 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 getProject 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 getProject. 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.
getProject is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue