Returns metadata about a Databricks Genie Space.
AI agents call get_space_info to retrieve information from databricks-genie-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a space without creating, modifying, deleting, or executing any operations. It is a straightforward data query with no side effects, fitting the Read category. Severity is low because metadata retrieval poses minimal risk—it may expose some organizational structure or configuration details, but cannot alter systems or trigger external operations.
From the tool's definition Tool returns metadata about a Databricks Genie Space with no indication of modification, deletion, or execution capabilities. The verb 'Returns' and the term 'metadata' indicate read-only retrieval.
Documented attack patterns abuse exactly the kind of access get_space_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and databricks-genie-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_space_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_space_info": {}
}
}get_space_info 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.
Returns metadata about a Databricks Genie Space. It is categorised as a Read tool in the databricks-genie-MCP MCP Server, which means it retrieves data without modifying state.
Register the databricks-genie- MCP server in PolicyLayer and add a rule for get_space_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 databricks-genie-MCP. Nothing to install.
get_space_info 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_space_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 get_space_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.
get_space_info is provided by the databricks-genie- MCP server (yashshingvi/databricks-genie-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from databricks-genie-MCP, 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.
3 databricks-genie-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.