science.materials.details
Get full DFT-computed properties for a material by Materials Project ID (e.g. mp-149 for silicon). Returns: band gap, formation energy, thermodynamic stability, density, crystal structure, spacegroup, magnetism, bulk/shear modulus, Poisson ratio, Fermi energy, database cross-references. 150K+ mat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/science.materials.details.md
What science.materials.details does on Apibase
AI agents call science.materials.details to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
material_id | string | Yes | Materials Project ID (e.g. "mp-149" for silicon, "mp-19017" for LiFePO4). Get IDs from materials.search |
Parameters from the server's own tool schema.
Why science.materials.details is rated Low
Tool retrieves pre-computed materials science data with no side effects or modifications.
From the tool's definition Get full DFT-computed properties, Returns: band gap, formation energy, density, crystal structure
Attacks that exploit this kind of access
The rule that runs science.materials.details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For science.materials.details, this is the rule to start with:
science.materials.details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every science.materials.details call is checked against it from then on.
Questions about science.materials.details
Get full DFT-computed properties for a material by Materials Project ID (e.g. mp-149 for silicon). Returns: band gap, formation energy, thermodynamic stability, density, crystal structure, spacegroup, magnetism, bulk/shear modulus, Poisson ratio, Fermi energy, database cross-references. 150K+ materials (Materials Project). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
science.materials.details accepts 1 parameter: material_id. Required: material_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for science.materials.details: 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 Apibase. Nothing to install.
science.materials.details 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 science.materials.details 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 science.materials.details. 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.
science.materials.details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue