AI agents call get-project-config to retrieve information from BaaS-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration state and implementation rules without modifying or deleting any data. It is a read-only verification/inspection operation. The mention of 'confirming' project ID settings and 'loading' rules indicates data retrieval. No side effects, no data creation, modification, deletion, or execution of arbitrary operations. Low severity due to confined scope of querying internal configuration.
From the tool's definition Tool performs initial configuration verification ('초기 설정을 확인합니다' / 'check initial setup'). It retrieves and confirms project ID settings and loads implementation rules.
Attacks that exploit this kind of access
BaaS MCP 초기 설정을 확인합니다. 중요: 모든 기능 구현 전에 먼저 이 도구를 실행하여 다음을 확인하세요: 1. 프로젝트 ID 설정 확인 2. 필수 구현 규칙 로드 (보안, 에러 처리, 상태 관리) 이 도구가 제공하는 필수 규칙은 모든 API 구현에 반드시 적용되어야 합니다. It is categorised as a Read tool in the BaaS-MCP MCP Server, which means it retrieves data without modifying state.
Register the BaaS- MCP server in PolicyLayer and add a rule for get-project-config: 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 BaaS-MCP. Nothing to install.
get-project-config 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-config 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-config. 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-config is provided by the BaaS- MCP server (mbaas-inc/baas-mcp). 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 →