get_jama_item_downstream_related
AI agents call get_jama_item_downstream_related to retrieve information from Jama without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves downstream relationship data from a Jama Connect instance. The 'get' prefix combined with the server's read-only design confirms it performs a query operation with no side effects. The empty description lowers confidence slightly, but the server-level read-only constraint and sibling tools (all prefixed with 'get_') reinforce the Read classification.
From the tool's definition Server is explicitly described as 'Read-only MCP server'; tool name 'get_jama_item_downstream_related' uses 'get' verb indicating data retrieval with no modification capability.
Documented attack patterns abuse exactly the kind of access get_jama_item_downstream_related gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jama, and nothing reaches the server without passing your rules. This is the rule we recommend for get_jama_item_downstream_related:
{
"version": "1",
"default": "deny",
"tools": {
"get_jama_item_downstream_related": {}
}
}get_jama_item_downstream_related 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_jama_item_downstream_related. It is categorised as a Read tool in the Jama MCP Server, which means it retrieves data without modifying state.
Register the Jama MCP server in PolicyLayer and add a rule for get_jama_item_downstream_related: 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 Jama. Nothing to install.
get_jama_item_downstream_related 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_jama_item_downstream_related 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_jama_item_downstream_related. 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_jama_item_downstream_related is provided by the Jama MCP server (t-j-thomas/jama-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jama, 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.
21 Jama tools catalogued and risk-classified — across an index of 43,000+ MCP servers.