get_project_by_name
[MAINTENANCE] Read-only: Find a project by name — look up, search, or resolve a project's project_id from its name (case-insensitive substring match). Use when the user names a project but you need its id. Returns the first hit with id, name, and sprint.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-project-by-name.md
What get_project_by_name does on Meridian
AI agents call get_project_by_name to retrieve information from Meridian 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 |
|---|---|---|---|
name | string | Yes |
Parameters from the server's own tool schema.
Why get_project_by_name is rated Low
This tool performs a query operation to retrieve project metadata by name. It has no side effects—it does not create, modify, delete, or execute any operations. The explicit 'Read-only' designation and use case (resolving identifiers for lookup) place it squarely in the Read category.
From the tool's definition The tool description explicitly states '[MAINTENANCE] Read-only: Find a project by name — look up, search, or resolve a project's project_id from its name'.
Attacks that exploit this kind of access
The rule that runs get_project_by_name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_project_by_name, this is the rule to start with:
get_project_by_name 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 Meridian, apply this rule, and every get_project_by_name call is checked against it from then on.
Questions about get_project_by_name
[MAINTENANCE] Read-only: Find a project by name — look up, search, or resolve a project's project_id from its name (case-insensitive substring match). Use when the user names a project but you need its id. Returns the first hit with id, name, and sprint. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_project_by_name accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for get_project_by_name: 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 Meridian. Nothing to install.
get_project_by_name 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_by_name 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_by_name. 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_by_name is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue