Get detailed information about a specific project including DSN
AI agents call get_project to retrieve information from Bugsink MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project metadata including a DSN (Data Source Name), which is read-only information lookup. There is no data modification, deletion, code execution, or financial transaction involved. The inclusion of DSN exposure is a security concern but does not change the category from Read—DSN disclosure is a consequence of read access, not a separate capability.
From the tool's definition Tool name is 'get_project' and description states 'Get detailed information about a specific project'. The server description confirms the purpose is to 'query and analyze errors' with operations like 'listing projects' and 'viewing detailed error events'.
Documented attack patterns abuse exactly the kind of access get_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bugsink MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project:
{
"version": "1",
"default": "deny",
"tools": {
"get_project": {}
}
}get_project is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific project including DSN. It is categorised as a Read tool in the Bugsink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bugsink MCP Server MCP server in PolicyLayer and add a rule for get_project: 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 Bugsink MCP Server. Nothing to install.
get_project 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 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. 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 is provided by the Bugsink MCP Server MCP server (j-shelfwood/bugsink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bugsink MCP 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.
16 Bugsink MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.