AI agents call get_projects to retrieve information from Datagsm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries project data from DataGSM with optional filtering parameters. It performs no side effects, creates no data, executes no code, and makes no modifications. It is a standard read operation consistent with sibling tools like get_students, get_clubs, get_meals which are also retrieval endpoints.
From the tool's definition Tool name 'get_projects' and description indicating it 'queries project list' (조회합니다) from DataGSM with filtering options by club and status. The verb '조회' (query/retrieve) indicates data retrieval with no modification.
Attacks that exploit this kind of access
DataGSM에서 프로젝트 목록을 조회합니다. 동아리별, 상태별로 필터링할 수 있습니다. It is categorised as a Read tool in the Datagsm MCP Server, which means it retrieves data without modifying state.
Register the Datagsm MCP server in PolicyLayer and add a rule for get_projects: 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 Datagsm. Nothing to install.
get_projects 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_projects 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_projects. 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_projects is provided by the Datagsm MCP server (snowykte0426/datagsm-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 →