Get or set project information in configuration file
AI agents use project_info to create or update resources in MCP Project Standards Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Project Standards Server environment.
This tool performs both read operations ('Get') and write operations ('set'). The write capability to modify project configuration files makes it a Write category tool rather than Read-only. Severity is medium because misconfigured project settings could impact development practices and team workflows, but it doesn't involve destructive deletion, code execution, or financial operations.
From the tool's definition Tool description states 'Get or set project information in configuration file' - the 'set' capability indicates modification of configuration data.
Documented attack patterns abuse exactly the kind of access project_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Standards Server, and nothing reaches the server without passing your rules. This is the rule we recommend for project_info:
{
"version": "1",
"default": "deny",
"tools": {
"project_info": {
"limits": [
{
"counter": "project_info_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} project_info stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get or set project information in configuration file. It is categorised as a Write tool in the MCP Project Standards Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Project Standards Server MCP server in PolicyLayer and add a rule for project_info: 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 MCP Project Standards Server. Nothing to install.
project_info is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the project_info 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 project_info. 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.
project_info is provided by the MCP Project Standards Server MCP server (liliangshan/mcp-server-project-standards). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Project Standards Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 MCP Project Standards Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.